diff options
| author | Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org> | 2014-08-21 17:51:45 +0200 |
|---|---|---|
| committer | Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org> | 2014-08-21 17:51:45 +0200 |
| commit | 5f000af75ed2cdfcec1b190b76d6cf8ee9cc9c0c (patch) | |
| tree | 7216a4c8251bee4a1e0159de03e745ac22057791 | |
| parent | cb044d4590c00625ea5f1d20c4ec144e03920aab (diff) | |
| download | aarch64-linux-android-4.9-linaro-5f000af75ed2cdfcec1b190b76d6cf8ee9cc9c0c.tar.gz | |
Add fix for bug 373
Source:
https://android-build.linaro.org/builds/~linaro-android/toolchain64-4.9-2014.08/#build=3
Signed-off-by: Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org>
100 files changed, 5262 insertions, 4705 deletions
diff --git a/aarch64-linux-android/lib64/libatomic.a b/aarch64-linux-android/lib64/libatomic.a Binary files differindex 00cb6f7..d87580b 100644 --- a/aarch64-linux-android/lib64/libatomic.a +++ b/aarch64-linux-android/lib64/libatomic.a diff --git a/aarch64-linux-android/lib64/libgomp.a b/aarch64-linux-android/lib64/libgomp.a Binary files differindex 3bb0ad9..7e7a643 100644 --- a/aarch64-linux-android/lib64/libgomp.a +++ b/aarch64-linux-android/lib64/libgomp.a diff --git a/aarch64-none-elf/bin/ar b/aarch64-none-elf/bin/ar Binary files differindex f6e92c7..63d205d 100755 --- a/aarch64-none-elf/bin/ar +++ b/aarch64-none-elf/bin/ar diff --git a/aarch64-none-elf/bin/as b/aarch64-none-elf/bin/as Binary files differindex 521ef97..0a95331 100755 --- a/aarch64-none-elf/bin/as +++ b/aarch64-none-elf/bin/as diff --git a/aarch64-none-elf/bin/ld b/aarch64-none-elf/bin/ld Binary files differindex 8f43e41..48748b1 100755 --- a/aarch64-none-elf/bin/ld +++ b/aarch64-none-elf/bin/ld diff --git a/aarch64-none-elf/bin/ld.bfd b/aarch64-none-elf/bin/ld.bfd Binary files differindex 8f43e41..48748b1 100755 --- a/aarch64-none-elf/bin/ld.bfd +++ b/aarch64-none-elf/bin/ld.bfd diff --git a/aarch64-none-elf/bin/nm b/aarch64-none-elf/bin/nm Binary files differindex 7c05bef..964c1d1 100755 --- a/aarch64-none-elf/bin/nm +++ b/aarch64-none-elf/bin/nm diff --git a/aarch64-none-elf/bin/objcopy b/aarch64-none-elf/bin/objcopy Binary files differindex 36b666c..cb950da 100755 --- a/aarch64-none-elf/bin/objcopy +++ b/aarch64-none-elf/bin/objcopy diff --git a/aarch64-none-elf/bin/objdump b/aarch64-none-elf/bin/objdump Binary files differindex 4030875..b0ef6c2 100755 --- a/aarch64-none-elf/bin/objdump +++ b/aarch64-none-elf/bin/objdump diff --git a/aarch64-none-elf/bin/ranlib b/aarch64-none-elf/bin/ranlib Binary files differindex c5cf72b..e183859 100755 --- a/aarch64-none-elf/bin/ranlib +++ b/aarch64-none-elf/bin/ranlib diff --git a/aarch64-none-elf/bin/strip b/aarch64-none-elf/bin/strip Binary files differindex 071a636..5940a76 100755 --- a/aarch64-none-elf/bin/strip +++ b/aarch64-none-elf/bin/strip diff --git a/bin/aarch64-elf-linux-android-gdb b/bin/aarch64-elf-linux-android-gdb Binary files differindex 0e5496e..10d5309 100755 --- a/bin/aarch64-elf-linux-android-gdb +++ b/bin/aarch64-elf-linux-android-gdb diff --git a/bin/aarch64-linux-android-c++ b/bin/aarch64-linux-android-c++ Binary files differindex 8cee74c..9e70152 100755 --- a/bin/aarch64-linux-android-c++ +++ b/bin/aarch64-linux-android-c++ diff --git a/bin/aarch64-linux-android-cpp b/bin/aarch64-linux-android-cpp Binary files differindex e3ecd0a..b116fe8 100755 --- a/bin/aarch64-linux-android-cpp +++ b/bin/aarch64-linux-android-cpp diff --git a/bin/aarch64-linux-android-g++ b/bin/aarch64-linux-android-g++ Binary files differindex 8cee74c..9e70152 100755 --- a/bin/aarch64-linux-android-g++ +++ b/bin/aarch64-linux-android-g++ diff --git a/bin/aarch64-linux-android-gcc b/bin/aarch64-linux-android-gcc Binary files differindex 74bd5fd..d58cd95 100755 --- a/bin/aarch64-linux-android-gcc +++ b/bin/aarch64-linux-android-gcc diff --git a/bin/aarch64-linux-android-gcc-4.9.2 b/bin/aarch64-linux-android-gcc-4.9.2 Binary files differindex 74bd5fd..d58cd95 100755 --- a/bin/aarch64-linux-android-gcc-4.9.2 +++ b/bin/aarch64-linux-android-gcc-4.9.2 diff --git a/bin/aarch64-none-elf-addr2line b/bin/aarch64-none-elf-addr2line Binary files differindex a599b40..c3eb138 100755 --- a/bin/aarch64-none-elf-addr2line +++ b/bin/aarch64-none-elf-addr2line diff --git a/bin/aarch64-none-elf-ar b/bin/aarch64-none-elf-ar Binary files differindex f6e92c7..63d205d 100755 --- a/bin/aarch64-none-elf-ar +++ b/bin/aarch64-none-elf-ar diff --git a/bin/aarch64-none-elf-as b/bin/aarch64-none-elf-as Binary files differindex 521ef97..0a95331 100755 --- a/bin/aarch64-none-elf-as +++ b/bin/aarch64-none-elf-as diff --git a/bin/aarch64-none-elf-c++ b/bin/aarch64-none-elf-c++ Binary files differindex a3b74f8..c15bf0d 100755 --- a/bin/aarch64-none-elf-c++ +++ b/bin/aarch64-none-elf-c++ diff --git a/bin/aarch64-none-elf-c++filt b/bin/aarch64-none-elf-c++filt Binary files differindex be8fb22..a20dba5 100755 --- a/bin/aarch64-none-elf-c++filt +++ b/bin/aarch64-none-elf-c++filt diff --git a/bin/aarch64-none-elf-cpp b/bin/aarch64-none-elf-cpp Binary files differindex ce8f3d1..eff4822 100755 --- a/bin/aarch64-none-elf-cpp +++ b/bin/aarch64-none-elf-cpp diff --git a/bin/aarch64-none-elf-elfedit b/bin/aarch64-none-elf-elfedit Binary files differindex e318810..063670c 100755 --- a/bin/aarch64-none-elf-elfedit +++ b/bin/aarch64-none-elf-elfedit diff --git a/bin/aarch64-none-elf-g++ b/bin/aarch64-none-elf-g++ Binary files differindex a3b74f8..c15bf0d 100755 --- a/bin/aarch64-none-elf-g++ +++ b/bin/aarch64-none-elf-g++ diff --git a/bin/aarch64-none-elf-gcc b/bin/aarch64-none-elf-gcc Binary files differindex 135873a..7888bed 100755 --- a/bin/aarch64-none-elf-gcc +++ b/bin/aarch64-none-elf-gcc diff --git a/bin/aarch64-none-elf-gcc-4.9.2 b/bin/aarch64-none-elf-gcc-4.9.2 Binary files differnew file mode 100755 index 0000000..7888bed --- /dev/null +++ b/bin/aarch64-none-elf-gcc-4.9.2 diff --git a/bin/aarch64-none-elf-gcc-ar b/bin/aarch64-none-elf-gcc-ar Binary files differindex 058c4b4..8922f9e 100755 --- a/bin/aarch64-none-elf-gcc-ar +++ b/bin/aarch64-none-elf-gcc-ar diff --git a/bin/aarch64-none-elf-gcc-nm b/bin/aarch64-none-elf-gcc-nm Binary files differindex 5cdd24a..12e22b5 100755 --- a/bin/aarch64-none-elf-gcc-nm +++ b/bin/aarch64-none-elf-gcc-nm diff --git a/bin/aarch64-none-elf-gcc-ranlib b/bin/aarch64-none-elf-gcc-ranlib Binary files differindex 713c447..de71e72 100755 --- a/bin/aarch64-none-elf-gcc-ranlib +++ b/bin/aarch64-none-elf-gcc-ranlib diff --git a/bin/aarch64-none-elf-gcov b/bin/aarch64-none-elf-gcov Binary files differindex ddc32bb..1fbdc57 100755 --- a/bin/aarch64-none-elf-gcov +++ b/bin/aarch64-none-elf-gcov diff --git a/bin/aarch64-none-elf-gprof b/bin/aarch64-none-elf-gprof Binary files differindex d634f21..0ea4eda 100755 --- a/bin/aarch64-none-elf-gprof +++ b/bin/aarch64-none-elf-gprof diff --git a/bin/aarch64-none-elf-ld b/bin/aarch64-none-elf-ld Binary files differindex 8f43e41..48748b1 100755 --- a/bin/aarch64-none-elf-ld +++ b/bin/aarch64-none-elf-ld diff --git a/bin/aarch64-none-elf-ld.bfd b/bin/aarch64-none-elf-ld.bfd Binary files differindex 8f43e41..48748b1 100755 --- a/bin/aarch64-none-elf-ld.bfd +++ b/bin/aarch64-none-elf-ld.bfd diff --git a/bin/aarch64-none-elf-nm b/bin/aarch64-none-elf-nm Binary files differindex 7c05bef..964c1d1 100755 --- a/bin/aarch64-none-elf-nm +++ b/bin/aarch64-none-elf-nm diff --git a/bin/aarch64-none-elf-objcopy b/bin/aarch64-none-elf-objcopy Binary files differindex 36b666c..cb950da 100755 --- a/bin/aarch64-none-elf-objcopy +++ b/bin/aarch64-none-elf-objcopy diff --git a/bin/aarch64-none-elf-objdump b/bin/aarch64-none-elf-objdump Binary files differindex 4030875..b0ef6c2 100755 --- a/bin/aarch64-none-elf-objdump +++ b/bin/aarch64-none-elf-objdump diff --git a/bin/aarch64-none-elf-ranlib b/bin/aarch64-none-elf-ranlib Binary files differindex c5cf72b..e183859 100755 --- a/bin/aarch64-none-elf-ranlib +++ b/bin/aarch64-none-elf-ranlib diff --git a/bin/aarch64-none-elf-readelf b/bin/aarch64-none-elf-readelf Binary files differindex ce85967..4a8c01e 100755 --- a/bin/aarch64-none-elf-readelf +++ b/bin/aarch64-none-elf-readelf diff --git a/bin/aarch64-none-elf-size b/bin/aarch64-none-elf-size Binary files differindex dd8cf0e..9a224ba 100755 --- a/bin/aarch64-none-elf-size +++ b/bin/aarch64-none-elf-size diff --git a/bin/aarch64-none-elf-strings b/bin/aarch64-none-elf-strings Binary files differindex 2822782..e770778 100755 --- a/bin/aarch64-none-elf-strings +++ b/bin/aarch64-none-elf-strings diff --git a/bin/aarch64-none-elf-strip b/bin/aarch64-none-elf-strip Binary files differindex 071a636..5940a76 100755 --- a/bin/aarch64-none-elf-strip +++ b/bin/aarch64-none-elf-strip diff --git a/lib/gcc/aarch64-linux-android/4.9.2/include/omp.h b/lib/gcc/aarch64-linux-android/4.9.2/include/omp.h new file mode 100644 index 0000000..9bcceb5 --- /dev/null +++ b/lib/gcc/aarch64-linux-android/4.9.2/include/omp.h @@ -0,0 +1,127 @@ +/* Copyright (C) 2005-2014 Free Software Foundation, Inc. + Contributed by Richard Henderson <rth@redhat.com>. + + This file is part of the GNU OpenMP Library (libgomp). + + Libgomp 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. + + Libgomp 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. + + 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 + <http://www.gnu.org/licenses/>. */ + +#ifndef _OMP_H +#define _OMP_H 1 + +#ifndef _LIBGOMP_OMP_LOCK_DEFINED +#define _LIBGOMP_OMP_LOCK_DEFINED 1 +/* These two structures get edited by the libgomp build process to + reflect the shape of the two types. Their internals are private + to the library. */ + +typedef struct +{ + unsigned char _x[4] + __attribute__((__aligned__(4))); +} omp_lock_t; + +typedef struct +{ + unsigned char _x[16] + __attribute__((__aligned__(8))); +} omp_nest_lock_t; +#endif + +typedef enum omp_sched_t +{ + omp_sched_static = 1, + omp_sched_dynamic = 2, + omp_sched_guided = 3, + omp_sched_auto = 4 +} omp_sched_t; + +typedef enum omp_proc_bind_t +{ + omp_proc_bind_false = 0, + omp_proc_bind_true = 1, + omp_proc_bind_master = 2, + omp_proc_bind_close = 3, + omp_proc_bind_spread = 4 +} omp_proc_bind_t; + +#ifdef __cplusplus +extern "C" { +# define __GOMP_NOTHROW throw () +#else +# define __GOMP_NOTHROW __attribute__((__nothrow__)) +#endif + +extern void omp_set_num_threads (int) __GOMP_NOTHROW; +extern int omp_get_num_threads (void) __GOMP_NOTHROW; +extern int omp_get_max_threads (void) __GOMP_NOTHROW; +extern int omp_get_thread_num (void) __GOMP_NOTHROW; +extern int omp_get_num_procs (void) __GOMP_NOTHROW; + +extern int omp_in_parallel (void) __GOMP_NOTHROW; + +extern void omp_set_dynamic (int) __GOMP_NOTHROW; +extern int omp_get_dynamic (void) __GOMP_NOTHROW; + +extern void omp_set_nested (int) __GOMP_NOTHROW; +extern int omp_get_nested (void) __GOMP_NOTHROW; + +extern void omp_init_lock (omp_lock_t *) __GOMP_NOTHROW; +extern void omp_destroy_lock (omp_lock_t *) __GOMP_NOTHROW; +extern void omp_set_lock (omp_lock_t *) __GOMP_NOTHROW; +extern void omp_unset_lock (omp_lock_t *) __GOMP_NOTHROW; +extern int omp_test_lock (omp_lock_t *) __GOMP_NOTHROW; + +extern void omp_init_nest_lock (omp_nest_lock_t *) __GOMP_NOTHROW; +extern void omp_destroy_nest_lock (omp_nest_lock_t *) __GOMP_NOTHROW; +extern void omp_set_nest_lock (omp_nest_lock_t *) __GOMP_NOTHROW; +extern void omp_unset_nest_lock (omp_nest_lock_t *) __GOMP_NOTHROW; +extern int omp_test_nest_lock (omp_nest_lock_t *) __GOMP_NOTHROW; + +extern double omp_get_wtime (void) __GOMP_NOTHROW; +extern double omp_get_wtick (void) __GOMP_NOTHROW; + +extern void omp_set_schedule (omp_sched_t, int) __GOMP_NOTHROW; +extern void omp_get_schedule (omp_sched_t *, int *) __GOMP_NOTHROW; +extern int omp_get_thread_limit (void) __GOMP_NOTHROW; +extern void omp_set_max_active_levels (int) __GOMP_NOTHROW; +extern int omp_get_max_active_levels (void) __GOMP_NOTHROW; +extern int omp_get_level (void) __GOMP_NOTHROW; +extern int omp_get_ancestor_thread_num (int) __GOMP_NOTHROW; +extern int omp_get_team_size (int) __GOMP_NOTHROW; +extern int omp_get_active_level (void) __GOMP_NOTHROW; + +extern int omp_in_final (void) __GOMP_NOTHROW; + +extern int omp_get_cancellation (void) __GOMP_NOTHROW; +extern omp_proc_bind_t omp_get_proc_bind (void) __GOMP_NOTHROW; + +extern void omp_set_default_device (int) __GOMP_NOTHROW; +extern int omp_get_default_device (void) __GOMP_NOTHROW; +extern int omp_get_num_devices (void) __GOMP_NOTHROW; +extern int omp_get_num_teams (void) __GOMP_NOTHROW; +extern int omp_get_team_num (void) __GOMP_NOTHROW; + +extern int omp_is_initial_device (void) __GOMP_NOTHROW; + +#ifdef __cplusplus +} +#endif + +#endif /* _OMP_H */ diff --git a/lib/gcc/aarch64-linux-android/4.9.2/libgcc.a b/lib/gcc/aarch64-linux-android/4.9.2/libgcc.a Binary files differindex 315aaf0..1d0ee23 100644 --- a/lib/gcc/aarch64-linux-android/4.9.2/libgcc.a +++ b/lib/gcc/aarch64-linux-android/4.9.2/libgcc.a diff --git a/lib/gcc/aarch64-linux-android/4.9.2/libgcov.a b/lib/gcc/aarch64-linux-android/4.9.2/libgcov.a Binary files differindex 0d70035..51da472 100644 --- a/lib/gcc/aarch64-linux-android/4.9.2/libgcov.a +++ b/lib/gcc/aarch64-linux-android/4.9.2/libgcov.a diff --git a/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/configargs.h b/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/configargs.h index 106a470..52fabdd 100644 --- a/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/configargs.h +++ b/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/configargs.h @@ -1,5 +1,5 @@ /* Generated automatically. */ -static const char configuration_arguments[] = "/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/../build/../gcc/gcc-linaro-4.9-2014.08/configure --prefix=/tmp/android-toolchain-eabi --host=x86_64-linux-gnu --build=x86_64-linux-gnu --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --with-gmp=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/temp-install --with-mpfr=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/temp-install --with-mpc=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/temp-install --disable-libssp --disable-nls --disable-libmudflap --disable-shared --disable-sjlj-exceptions --disable-libquadmath --disable-libitm --disable-libsanitizer --prefix=/tmp/android-toolchain-eabi --disable-docs --disable-nls --with-gcc-version=linaro-4.9-2014.08 --with-binutils-version=current --with-gmp-version=current --with-mpfr-version=current --with-mpc-version=current --disable-graphite --target=aarch64-linux-android --enable-threads --enable-tls --disable-libgomp --disable-libstdc__-v3 --disable-libitm --disable-libsanitizer --disable-libatomic"; +static const char configuration_arguments[] = "/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/../build/../gcc/gcc-linaro-4.9-2014.08/configure --prefix=/tmp/android-toolchain-eabi --host=x86_64-linux-gnu --build=x86_64-linux-gnu --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --with-gmp=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/temp-install --with-mpfr=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/temp-install --with-mpc=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/temp-install --disable-libssp --disable-nls --disable-libmudflap --disable-shared --disable-sjlj-exceptions --disable-libquadmath --disable-libitm --disable-libsanitizer --prefix=/tmp/android-toolchain-eabi --disable-docs --disable-nls --with-gcc-version=linaro-4.9-2014.08 --with-binutils-version=current --with-gmp-version=current --with-mpfr-version=current --with-mpc-version=current --disable-graphite --target=aarch64-linux-android --enable-threads --enable-tls --enable-libgomp --disable-libitm --disable-libsanitizer --enable-libatomic --disable-libstdc__-v3 : (reconfigured) /mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/../build/../gcc/gcc-linaro-4.9-2014.08/configure --prefix=/tmp/android-toolchain-eabi --host=x86_64-linux-gnu --build=x86_64-linux-gnu --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --with-gmp=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/temp-install --with-mpfr=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/temp-install --with-mpc=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/temp-install --disable-libssp --disable-nls --disable-libmudflap --disable-shared --disable-sjlj-exceptions --disable-libquadmath --disable-libitm --disable-libsanitizer --prefix=/tmp/android-toolchain-eabi --disable-docs --disable-nls --with-gcc-version=linaro-4.9-2014.08 --with-binutils-version=current --with-gmp-version=current --with-mpfr-version=current --with-mpc-version=current --disable-graphite --target=aarch64-linux-android --enable-threads --enable-tls --enable-libgomp --disable-libitm --disable-libsanitizer --enable-libatomic --disable-libstdc__-v3"; static const char thread_model[] = "posix"; static const struct { diff --git a/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/insn-codes.h b/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/insn-codes.h index c4e7b9e..91cd9b0 100644 --- a/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/insn-codes.h +++ b/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/insn-codes.h @@ -464,14 +464,14 @@ enum insn_code { CODE_FOR_move_lo_quad_internal_v16qi = 1017, CODE_FOR_move_lo_quad_internal_v8hi = 1018, CODE_FOR_move_lo_quad_internal_v4si = 1019, - CODE_FOR_move_lo_quad_internal_v2di = 1020, - CODE_FOR_move_lo_quad_internal_v4sf = 1021, + CODE_FOR_move_lo_quad_internal_v4sf = 1020, + CODE_FOR_move_lo_quad_internal_v2di = 1021, CODE_FOR_move_lo_quad_internal_v2df = 1022, CODE_FOR_move_lo_quad_internal_be_v16qi = 1023, CODE_FOR_move_lo_quad_internal_be_v8hi = 1024, CODE_FOR_move_lo_quad_internal_be_v4si = 1025, - CODE_FOR_move_lo_quad_internal_be_v2di = 1026, - CODE_FOR_move_lo_quad_internal_be_v4sf = 1027, + CODE_FOR_move_lo_quad_internal_be_v4sf = 1026, + CODE_FOR_move_lo_quad_internal_be_v2di = 1027, CODE_FOR_move_lo_quad_internal_be_v2df = 1028, CODE_FOR_aarch64_simd_move_hi_quad_v16qi = 1029, CODE_FOR_aarch64_simd_move_hi_quad_v8hi = 1030, diff --git a/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/insn-flags.h b/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/insn-flags.h index 262bef5..156331e 100644 --- a/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/insn-flags.h +++ b/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/insn-flags.h @@ -491,14 +491,14 @@ #define HAVE_move_lo_quad_internal_v16qi (TARGET_SIMD && !BYTES_BIG_ENDIAN) #define HAVE_move_lo_quad_internal_v8hi (TARGET_SIMD && !BYTES_BIG_ENDIAN) #define HAVE_move_lo_quad_internal_v4si (TARGET_SIMD && !BYTES_BIG_ENDIAN) -#define HAVE_move_lo_quad_internal_v2di (TARGET_SIMD && !BYTES_BIG_ENDIAN) #define HAVE_move_lo_quad_internal_v4sf (TARGET_SIMD && !BYTES_BIG_ENDIAN) +#define HAVE_move_lo_quad_internal_v2di (TARGET_SIMD && !BYTES_BIG_ENDIAN) #define HAVE_move_lo_quad_internal_v2df (TARGET_SIMD && !BYTES_BIG_ENDIAN) #define HAVE_move_lo_quad_internal_be_v16qi (TARGET_SIMD && BYTES_BIG_ENDIAN) #define HAVE_move_lo_quad_internal_be_v8hi (TARGET_SIMD && BYTES_BIG_ENDIAN) #define HAVE_move_lo_quad_internal_be_v4si (TARGET_SIMD && BYTES_BIG_ENDIAN) -#define HAVE_move_lo_quad_internal_be_v2di (TARGET_SIMD && BYTES_BIG_ENDIAN) #define HAVE_move_lo_quad_internal_be_v4sf (TARGET_SIMD && BYTES_BIG_ENDIAN) +#define HAVE_move_lo_quad_internal_be_v2di (TARGET_SIMD && BYTES_BIG_ENDIAN) #define HAVE_move_lo_quad_internal_be_v2df (TARGET_SIMD && BYTES_BIG_ENDIAN) #define HAVE_aarch64_simd_move_hi_quad_v16qi (TARGET_SIMD && !BYTES_BIG_ENDIAN) #define HAVE_aarch64_simd_move_hi_quad_v8hi (TARGET_SIMD && !BYTES_BIG_ENDIAN) @@ -2890,14 +2890,14 @@ extern rtx gen_uminv4si3 (rtx, rtx, rtx); extern rtx gen_move_lo_quad_internal_v16qi (rtx, rtx); extern rtx gen_move_lo_quad_internal_v8hi (rtx, rtx); extern rtx gen_move_lo_quad_internal_v4si (rtx, rtx); -extern rtx gen_move_lo_quad_internal_v2di (rtx, rtx); extern rtx gen_move_lo_quad_internal_v4sf (rtx, rtx); +extern rtx gen_move_lo_quad_internal_v2di (rtx, rtx); extern rtx gen_move_lo_quad_internal_v2df (rtx, rtx); extern rtx gen_move_lo_quad_internal_be_v16qi (rtx, rtx); extern rtx gen_move_lo_quad_internal_be_v8hi (rtx, rtx); extern rtx gen_move_lo_quad_internal_be_v4si (rtx, rtx); -extern rtx gen_move_lo_quad_internal_be_v2di (rtx, rtx); extern rtx gen_move_lo_quad_internal_be_v4sf (rtx, rtx); +extern rtx gen_move_lo_quad_internal_be_v2di (rtx, rtx); extern rtx gen_move_lo_quad_internal_be_v2df (rtx, rtx); extern rtx gen_aarch64_simd_move_hi_quad_v16qi (rtx, rtx, rtx); extern rtx gen_aarch64_simd_move_hi_quad_v8hi (rtx, rtx, rtx); diff --git a/lib/libbfd.a b/lib/libbfd.a Binary files differindex 2b88162..46c8c24 100644 --- a/lib/libbfd.a +++ b/lib/libbfd.a diff --git a/lib/libiberty.a b/lib/libiberty.a Binary files differindex 67c8918..1005813 100644 --- a/lib/libiberty.a +++ b/lib/libiberty.a diff --git a/lib/libintl.a b/lib/libintl.a Binary files differindex 1a91357..145da98 100644 --- a/lib/libintl.a +++ b/lib/libintl.a diff --git a/libexec/gcc/aarch64-linux-android/4.9.2/cc1 b/libexec/gcc/aarch64-linux-android/4.9.2/cc1 Binary files differindex aff092b..06a7400 100755 --- a/libexec/gcc/aarch64-linux-android/4.9.2/cc1 +++ b/libexec/gcc/aarch64-linux-android/4.9.2/cc1 diff --git a/libexec/gcc/aarch64-linux-android/4.9.2/cc1plus b/libexec/gcc/aarch64-linux-android/4.9.2/cc1plus Binary files differindex c9b3d68..729cd1a 100755 --- a/libexec/gcc/aarch64-linux-android/4.9.2/cc1plus +++ b/libexec/gcc/aarch64-linux-android/4.9.2/cc1plus diff --git a/libexec/gcc/aarch64-linux-android/4.9.2/lto1 b/libexec/gcc/aarch64-linux-android/4.9.2/lto1 Binary files differindex 0ee361c..2be9a63 100755 --- a/libexec/gcc/aarch64-linux-android/4.9.2/lto1 +++ b/libexec/gcc/aarch64-linux-android/4.9.2/lto1 diff --git a/share/info/bfd.info b/share/info/bfd.info index e03eb87..91e2e92 100644 --- a/share/info/bfd.info +++ b/share/info/bfd.info @@ -1,5 +1,5 @@ This is bfd.info, produced by makeinfo version 4.13 from -/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/../build/../binutils/binutils-current/bfd/doc/bfd.texinfo. +/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/../build/../gdb/gdb-current/bfd/doc/bfd.texinfo. INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY @@ -345,14 +345,6 @@ major data about the file and pointers to the rest of the data. both_direction = 3 }; - enum bfd_lto_object_type - { - lto_non_object, - lto_non_ir_object, - lto_ir_object, - lto_mixed_object - }; - struct bfd { /* A unique identifier of the BFD */ @@ -500,9 +492,6 @@ major data about the file and pointers to the rest of the data. /* The last section on the section list. */ struct bfd_section *section_last; - /* The object-only section on the section list. */ - struct bfd_section *object_only_section; - /* The number of sections. */ unsigned int section_count; @@ -621,11 +610,16 @@ major data about the file and pointers to the rest of the data. /* Set if only required symbols should be added in the link hash table for this object. Used by VMS linkers. */ unsigned int selective_search : 1; - - /* LTO object type. */ - unsigned int lto_type : 2; }; + /* See note beside bfd_set_section_userdata. */ + static inline bfd_boolean + bfd_set_cacheable (bfd * abfd, bfd_boolean val) + { + abfd->cacheable = val; + return TRUE; + } + File: bfd.info, Node: Error reporting, Next: Miscellaneous, Prev: typedef bfd, Up: BFD front end @@ -1154,15 +1148,7 @@ such chars that would otherwise confuse the demangler. If passed a g++ v3 ABI mangled name, returns a buffer allocated with malloc holding the demangled name. Returns NULL otherwise and on memory alloc failure. -2.3.1.22 `bfd_group_signature' -.............................. - -*Synopsis* - asymbol *bfd_group_signature (asection *group, asymbol **isympp); - *Description* -Return a pointer to the symbol used as a signature for GROUP. - -2.3.1.23 `struct bfd_iovec' +2.3.1.22 `struct bfd_iovec' ........................... *Description* @@ -1202,7 +1188,7 @@ below). }; extern const struct bfd_iovec _bfd_memory_iovec; -2.3.1.24 `bfd_get_mtime' +2.3.1.23 `bfd_get_mtime' ........................ *Synopsis* @@ -1211,7 +1197,7 @@ below). Return the file modification time (as read from the file system, or from the archive header for archive members). -2.3.1.25 `bfd_get_size' +2.3.1.24 `bfd_get_size' ....................... *Synopsis* @@ -1240,7 +1226,7 @@ table, or a "virtual memory exhausted" error when it tries to allocate to read. This function at least allows us to answer the question, "is the size reasonable?". -2.3.1.26 `bfd_mmap' +2.3.1.25 `bfd_mmap' ................... *Synopsis* @@ -1808,6 +1794,32 @@ Here is the section structure: int size; }; + /* Note: the following are provided as inline functions rather than macros + because not all callers use the return value. A macro implementation + would use a comma expression, eg: "((ptr)->foo = val, TRUE)" and some + compilers will complain about comma expressions that have no effect. */ + static inline bfd_boolean + bfd_set_section_userdata (bfd * abfd ATTRIBUTE_UNUSED, asection * ptr, void * val) + { + ptr->userdata = val; + return TRUE; + } + + static inline bfd_boolean + bfd_set_section_vma (bfd * abfd ATTRIBUTE_UNUSED, asection * ptr, bfd_vma val) + { + ptr->vma = ptr->lma = val; + ptr->user_set_vma = TRUE; + return TRUE; + } + + static inline bfd_boolean + bfd_set_section_alignment (bfd * abfd ATTRIBUTE_UNUSED, asection * ptr, unsigned int val) + { + ptr->alignment_power = val; + return TRUE; + } + /* These sections are global, and are managed by BFD. The application and target back end are not permitted to change the values in these sections. */ @@ -1818,9 +1830,6 @@ Here is the section structure: #define BFD_COM_SECTION_NAME "*COM*" #define BFD_IND_SECTION_NAME "*IND*" - /* GNU object-only section name. */ - #define GNU_OBJECT_ONLY_SECTION_NAME ".gnu_object_only" - /* Pointer to the common section. */ #define bfd_com_section_ptr (&_bfd_std_section[0]) /* Pointer to the undefined section. */ @@ -2557,10 +2566,6 @@ An `asymbol' has the form: with this name and type in use. BSF_OBJECT must also be set. */ #define BSF_GNU_UNIQUE (1 << 23) - /* A secondary global symbol, overridable without warnings by - a regular or weak global symbol of the same name. */ - #define BSF_SECONDARY (1 << 24) - flagword flags; /* A pointer to the section to which this symbol is @@ -3819,6 +3824,7 @@ attributes. -- : BFD_RELOC_MICROMIPS_TLS_TPREL_HI16 -- : BFD_RELOC_MIPS_TLS_TPREL_LO16 -- : BFD_RELOC_MICROMIPS_TLS_TPREL_LO16 + -- : BFD_RELOC_MIPS_EH MIPS ELF relocations. -- : BFD_RELOC_MIPS_COPY @@ -3977,6 +3983,8 @@ attributes. -- : BFD_RELOC_X86_64_TLSDESC_CALL -- : BFD_RELOC_X86_64_TLSDESC -- : BFD_RELOC_X86_64_IRELATIVE + -- : BFD_RELOC_X86_64_PC32_BND + -- : BFD_RELOC_X86_64_PLT32_BND x86-64/elf relocations -- : BFD_RELOC_NS32K_IMM_8 @@ -4075,6 +4083,8 @@ attributes. -- : BFD_RELOC_PPC64_TOC16_LO_DS -- : BFD_RELOC_PPC64_PLTGOT16_DS -- : BFD_RELOC_PPC64_PLTGOT16_LO_DS + -- : BFD_RELOC_PPC64_ADDR16_HIGH + -- : BFD_RELOC_PPC64_ADDR16_HIGHA Power(rs6000) and PowerPC relocations. -- : BFD_RELOC_PPC_TLS @@ -4119,6 +4129,10 @@ attributes. -- : BFD_RELOC_PPC64_DTPREL16_HIGHERA -- : BFD_RELOC_PPC64_DTPREL16_HIGHEST -- : BFD_RELOC_PPC64_DTPREL16_HIGHESTA + -- : BFD_RELOC_PPC64_TPREL16_HIGH + -- : BFD_RELOC_PPC64_TPREL16_HIGHA + -- : BFD_RELOC_PPC64_DTPREL16_HIGH + -- : BFD_RELOC_PPC64_DTPREL16_HIGHA PowerPC and PowerPC64 thread-local storage relocations. -- : BFD_RELOC_I370_D12 @@ -4637,6 +4651,179 @@ attributes. -- : BFD_RELOC_M32R_GOTPC_LO For PIC. + -- : BFD_RELOC_NDS32_20 + NDS32 relocs. This is a 20 bit absolute address. + + -- : BFD_RELOC_NDS32_9_PCREL + This is a 9-bit pc-relative reloc with the right 1 bit assumed to + be 0. + + -- : BFD_RELOC_NDS32_WORD_9_PCREL + This is a 9-bit pc-relative reloc with the right 1 bit assumed to + be 0. + + -- : BFD_RELOC_NDS32_15_PCREL + This is an 15-bit reloc with the right 1 bit assumed to be 0. + + -- : BFD_RELOC_NDS32_17_PCREL + This is an 17-bit reloc with the right 1 bit assumed to be 0. + + -- : BFD_RELOC_NDS32_25_PCREL + This is a 25-bit reloc with the right 1 bit assumed to be 0. + + -- : BFD_RELOC_NDS32_HI20 + This is a 20-bit reloc containing the high 20 bits of an address + used with the lower 12 bits + + -- : BFD_RELOC_NDS32_LO12S3 + This is a 12-bit reloc containing the lower 12 bits of an address + then shift right by 3. This is used with ldi,sdi... + + -- : BFD_RELOC_NDS32_LO12S2 + This is a 12-bit reloc containing the lower 12 bits of an address + then shift left by 2. This is used with lwi,swi... + + -- : BFD_RELOC_NDS32_LO12S1 + This is a 12-bit reloc containing the lower 12 bits of an address + then shift left by 1. This is used with lhi,shi... + + -- : BFD_RELOC_NDS32_LO12S0 + This is a 12-bit reloc containing the lower 12 bits of an address + then shift left by 0. This is used with lbisbi... + + -- : BFD_RELOC_NDS32_LO12S0_ORI + This is a 12-bit reloc containing the lower 12 bits of an address + then shift left by 0. This is only used with branch relaxations + + -- : BFD_RELOC_NDS32_SDA15S3 + This is a 15-bit reloc containing the small data area 18-bit + signed offset and shift left by 3 for use in ldi, sdi... + + -- : BFD_RELOC_NDS32_SDA15S2 + This is a 15-bit reloc containing the small data area 17-bit + signed offset and shift left by 2 for use in lwi, swi... + + -- : BFD_RELOC_NDS32_SDA15S1 + This is a 15-bit reloc containing the small data area 16-bit + signed offset and shift left by 1 for use in lhi, shi... + + -- : BFD_RELOC_NDS32_SDA15S0 + This is a 15-bit reloc containing the small data area 15-bit + signed offset and shift left by 0 for use in lbi, sbi... + + -- : BFD_RELOC_NDS32_SDA16S3 + This is a 16-bit reloc containing the small data area 16-bit + signed offset and shift left by 3 + + -- : BFD_RELOC_NDS32_SDA17S2 + This is a 17-bit reloc containing the small data area 17-bit + signed offset and shift left by 2 for use in lwi.gp, swi.gp... + + -- : BFD_RELOC_NDS32_SDA18S1 + This is a 18-bit reloc containing the small data area 18-bit + signed offset and shift left by 1 for use in lhi.gp, shi.gp... + + -- : BFD_RELOC_NDS32_SDA19S0 + This is a 19-bit reloc containing the small data area 19-bit + signed offset and shift left by 0 for use in lbi.gp, sbi.gp... + + -- : BFD_RELOC_NDS32_GOT20 + -- : BFD_RELOC_NDS32_9_PLTREL + -- : BFD_RELOC_NDS32_25_PLTREL + -- : BFD_RELOC_NDS32_COPY + -- : BFD_RELOC_NDS32_GLOB_DAT + -- : BFD_RELOC_NDS32_JMP_SLOT + -- : BFD_RELOC_NDS32_RELATIVE + -- : BFD_RELOC_NDS32_GOTOFF + -- : BFD_RELOC_NDS32_GOTOFF_HI20 + -- : BFD_RELOC_NDS32_GOTOFF_LO12 + -- : BFD_RELOC_NDS32_GOTPC20 + -- : BFD_RELOC_NDS32_GOT_HI20 + -- : BFD_RELOC_NDS32_GOT_LO12 + -- : BFD_RELOC_NDS32_GOTPC_HI20 + -- : BFD_RELOC_NDS32_GOTPC_LO12 + for PIC + + -- : BFD_RELOC_NDS32_INSN16 + -- : BFD_RELOC_NDS32_LABEL + -- : BFD_RELOC_NDS32_LONGCALL1 + -- : BFD_RELOC_NDS32_LONGCALL2 + -- : BFD_RELOC_NDS32_LONGCALL3 + -- : BFD_RELOC_NDS32_LONGJUMP1 + -- : BFD_RELOC_NDS32_LONGJUMP2 + -- : BFD_RELOC_NDS32_LONGJUMP3 + -- : BFD_RELOC_NDS32_LOADSTORE + -- : BFD_RELOC_NDS32_9_FIXED + -- : BFD_RELOC_NDS32_15_FIXED + -- : BFD_RELOC_NDS32_17_FIXED + -- : BFD_RELOC_NDS32_25_FIXED + for relax + + -- : BFD_RELOC_NDS32_PLTREL_HI20 + -- : BFD_RELOC_NDS32_PLTREL_LO12 + -- : BFD_RELOC_NDS32_PLT_GOTREL_HI20 + -- : BFD_RELOC_NDS32_PLT_GOTREL_LO12 + for PIC + + -- : BFD_RELOC_NDS32_SDA12S2_DP + -- : BFD_RELOC_NDS32_SDA12S2_SP + -- : BFD_RELOC_NDS32_LO12S2_DP + -- : BFD_RELOC_NDS32_LO12S2_SP + for floating point + + -- : BFD_RELOC_NDS32_DWARF2_OP1 + -- : BFD_RELOC_NDS32_DWARF2_OP2 + -- : BFD_RELOC_NDS32_DWARF2_LEB + for dwarf2 debug_line. + + -- : BFD_RELOC_NDS32_UPDATE_TA + for eliminate 16-bit instructions + + -- : BFD_RELOC_NDS32_PLT_GOTREL_LO20 + -- : BFD_RELOC_NDS32_PLT_GOTREL_LO15 + -- : BFD_RELOC_NDS32_PLT_GOTREL_LO19 + -- : BFD_RELOC_NDS32_GOT_LO15 + -- : BFD_RELOC_NDS32_GOT_LO19 + -- : BFD_RELOC_NDS32_GOTOFF_LO15 + -- : BFD_RELOC_NDS32_GOTOFF_LO19 + -- : BFD_RELOC_NDS32_GOT15S2 + -- : BFD_RELOC_NDS32_GOT17S2 + for PIC object relaxation + + -- : BFD_RELOC_NDS32_5 + NDS32 relocs. This is a 5 bit absolute address. + + -- : BFD_RELOC_NDS32_10_UPCREL + This is a 10-bit unsigned pc-relative reloc with the right 1 bit + assumed to be 0. + + -- : BFD_RELOC_NDS32_SDA_FP7U2_RELA + If fp were omitted, fp can used as another gp. + + -- : BFD_RELOC_NDS32_RELAX_ENTRY + -- : BFD_RELOC_NDS32_GOT_SUFF + -- : BFD_RELOC_NDS32_GOTOFF_SUFF + -- : BFD_RELOC_NDS32_PLT_GOT_SUFF + -- : BFD_RELOC_NDS32_MULCALL_SUFF + -- : BFD_RELOC_NDS32_PTR + -- : BFD_RELOC_NDS32_PTR_COUNT + -- : BFD_RELOC_NDS32_PTR_RESOLVED + -- : BFD_RELOC_NDS32_PLTBLOCK + -- : BFD_RELOC_NDS32_RELAX_REGION_BEGIN + -- : BFD_RELOC_NDS32_RELAX_REGION_END + -- : BFD_RELOC_NDS32_MINUEND + -- : BFD_RELOC_NDS32_SUBTRAHEND + -- : BFD_RELOC_NDS32_DIFF8 + -- : BFD_RELOC_NDS32_DIFF16 + -- : BFD_RELOC_NDS32_DIFF32 + -- : BFD_RELOC_NDS32_DIFF_ULEB128 + -- : BFD_RELOC_NDS32_25_ABS + -- : BFD_RELOC_NDS32_DATA + -- : BFD_RELOC_NDS32_TRAN + -- : BFD_RELOC_NDS32_17IFC_PCREL + -- : BFD_RELOC_NDS32_10IFCU_PCREL + relaxation relative relocation types + -- : BFD_RELOC_V850_9_PCREL This is a 9-bit reloc @@ -5187,12 +5374,24 @@ attributes. -- : BFD_RELOC_390_GOT16 16 bit GOT offset. + -- : BFD_RELOC_390_PC12DBL + PC relative 12 bit shifted by 1. + + -- : BFD_RELOC_390_PLT12DBL + 12 bit PC rel. PLT shifted by 1. + -- : BFD_RELOC_390_PC16DBL PC relative 16 bit shifted by 1. -- : BFD_RELOC_390_PLT16DBL 16 bit PC rel. PLT shifted by 1. + -- : BFD_RELOC_390_PC24DBL + PC relative 24 bit shifted by 1. + + -- : BFD_RELOC_390_PLT24DBL + 24 bit PC rel. PLT shifted by 1. + -- : BFD_RELOC_390_PC32DBL PC relative 32 bit shifted by 1. @@ -5784,6 +5983,21 @@ attributes. -- : BFD_RELOC_MSP430_16_BYTE -- : BFD_RELOC_MSP430_2X_PCREL -- : BFD_RELOC_MSP430_RL_PCREL + -- : BFD_RELOC_MSP430_ABS8 + -- : BFD_RELOC_MSP430X_PCR20_EXT_SRC + -- : BFD_RELOC_MSP430X_PCR20_EXT_DST + -- : BFD_RELOC_MSP430X_PCR20_EXT_ODST + -- : BFD_RELOC_MSP430X_ABS20_EXT_SRC + -- : BFD_RELOC_MSP430X_ABS20_EXT_DST + -- : BFD_RELOC_MSP430X_ABS20_EXT_ODST + -- : BFD_RELOC_MSP430X_ABS20_ADR_SRC + -- : BFD_RELOC_MSP430X_ABS20_ADR_DST + -- : BFD_RELOC_MSP430X_PCR16 + -- : BFD_RELOC_MSP430X_PCR20_CALL + -- : BFD_RELOC_MSP430X_ABS16 + -- : BFD_RELOC_MSP430_ABS_HI16 + -- : BFD_RELOC_MSP430_PREL31 + -- : BFD_RELOC_MSP430_SYM_DIFF msp430 specific relocation codes -- : BFD_RELOC_NIOS2_S16 @@ -6058,22 +6272,79 @@ attributes. This is a 64 bit reloc that stores 32-bit thread pointer relative offset to two words (uses imm instruction). - -- : BFD_RELOC_AARCH64_ADD_LO12 - AArch64 ADD immediate instruction, holding bits 0 to 11 of the - address. Used in conjunction with - BFD_RELOC_AARCH64_ADR_HI21_PCREL. + -- : BFD_RELOC_AARCH64_RELOC_START + AArch64 pseudo relocation code to mark the start of the AArch64 + relocation enumerators. N.B. the order of the enumerators is + important as several tables in the AArch64 bfd backend are indexed + by these enumerators; make sure they are all synced. - -- : BFD_RELOC_AARCH64_GOT_LD_PREL19 - AArch64 Load Literal instruction, holding a 19 bit PC relative word - offset of the global offset table entry for a symbol. The lowest - two bits must be zero and are not stored in the instruction, - giving a 21 bit signed byte offset. This relocation type requires - signed overflow checking. + -- : BFD_RELOC_AARCH64_NONE + AArch64 null relocation code. - -- : BFD_RELOC_AARCH64_ADR_GOT_PAGE - Get to the page base of the global offset table entry for a symbol - as part of an ADRP instruction using a 21 bit PC relative - value.Used in conjunction with BFD_RELOC_AARCH64_LD64_GOT_LO12_NC. + -- : BFD_RELOC_AARCH64_64 + -- : BFD_RELOC_AARCH64_32 + -- : BFD_RELOC_AARCH64_16 + Basic absolute relocations of N bits. These are equivalent to + BFD_RELOC_N and they were added to assist the indexing of the howto + table. + + -- : BFD_RELOC_AARCH64_64_PCREL + -- : BFD_RELOC_AARCH64_32_PCREL + -- : BFD_RELOC_AARCH64_16_PCREL + PC-relative relocations. These are equivalent to BFD_RELOC_N_PCREL + and they were added to assist the indexing of the howto table. + + -- : BFD_RELOC_AARCH64_MOVW_G0 + AArch64 MOV[NZK] instruction with most significant bits 0 to 15 of + an unsigned address/value. + + -- : BFD_RELOC_AARCH64_MOVW_G0_NC + AArch64 MOV[NZK] instruction with less significant bits 0 to 15 of + an address/value. No overflow checking. + + -- : BFD_RELOC_AARCH64_MOVW_G1 + AArch64 MOV[NZK] instruction with most significant bits 16 to 31 + of an unsigned address/value. + + -- : BFD_RELOC_AARCH64_MOVW_G1_NC + AArch64 MOV[NZK] instruction with less significant bits 16 to 31 + of an address/value. No overflow checking. + + -- : BFD_RELOC_AARCH64_MOVW_G2 + AArch64 MOV[NZK] instruction with most significant bits 32 to 47 + of an unsigned address/value. + + -- : BFD_RELOC_AARCH64_MOVW_G2_NC + AArch64 MOV[NZK] instruction with less significant bits 32 to 47 + of an address/value. No overflow checking. + + -- : BFD_RELOC_AARCH64_MOVW_G3 + AArch64 MOV[NZK] instruction with most signficant bits 48 to 64 of + a signed or unsigned address/value. + + -- : BFD_RELOC_AARCH64_MOVW_G0_S + AArch64 MOV[NZ] instruction with most significant bits 0 to 15 of + a signed value. Changes instruction to MOVZ or MOVN depending on + the value's sign. + + -- : BFD_RELOC_AARCH64_MOVW_G1_S + AArch64 MOV[NZ] instruction with most significant bits 16 to 31 of + a signed value. Changes instruction to MOVZ or MOVN depending on + the value's sign. + + -- : BFD_RELOC_AARCH64_MOVW_G2_S + AArch64 MOV[NZ] instruction with most significant bits 32 to 47 of + a signed value. Changes instruction to MOVZ or MOVN depending on + the value's sign. + + -- : BFD_RELOC_AARCH64_LD_LO19_PCREL + AArch64 Load Literal instruction, holding a 19 bit pc-relative word + offset. The lowest two bits must be zero and are not stored in the + instruction, giving a 21 bit signed byte offset. + + -- : BFD_RELOC_AARCH64_ADR_LO21_PCREL + AArch64 ADR instruction, holding a simple 21 bit pc-relative byte + offset. -- : BFD_RELOC_AARCH64_ADR_HI21_PCREL AArch64 ADRP instruction, with bits 12 to 32 of a pc-relative page @@ -6084,48 +6355,35 @@ attributes. offset, giving a 4KB aligned page base address, but with no overflow checking. - -- : BFD_RELOC_AARCH64_ADR_LO21_PCREL - AArch64 ADR instruction, holding a simple 21 bit pc-relative byte - offset. + -- : BFD_RELOC_AARCH64_ADD_LO12 + AArch64 ADD immediate instruction, holding bits 0 to 11 of the + address. Used in conjunction with + BFD_RELOC_AARCH64_ADR_HI21_PCREL. + + -- : BFD_RELOC_AARCH64_LDST8_LO12 + AArch64 8-bit load/store instruction, holding bits 0 to 11 of the + address. Used in conjunction with + BFD_RELOC_AARCH64_ADR_HI21_PCREL. + + -- : BFD_RELOC_AARCH64_TSTBR14 + AArch64 14 bit pc-relative test bit and branch. The lowest two + bits must be zero and are not stored in the instruction, giving a + 16 bit signed byte offset. -- : BFD_RELOC_AARCH64_BRANCH19 AArch64 19 bit pc-relative conditional branch and compare & branch. The lowest two bits must be zero and are not stored in the instruction, giving a 21 bit signed byte offset. - -- : BFD_RELOC_AARCH64_CALL26 - AArch64 26 bit pc-relative unconditional branch and link. The - lowest two bits must be zero and are not stored in the instruction, - giving a 28 bit signed byte offset. - - -- : BFD_RELOC_AARCH64_GAS_INTERNAL_FIXUP - AArch64 pseudo relocation code to be used internally by the AArch64 - assembler and not (currently) written to any object files. - -- : BFD_RELOC_AARCH64_JUMP26 AArch64 26 bit pc-relative unconditional branch. The lowest two bits must be zero and are not stored in the instruction, giving a 28 bit signed byte offset. - -- : BFD_RELOC_AARCH64_LD_LO19_PCREL - AArch64 Load Literal instruction, holding a 19 bit pc-relative word - offset. The lowest two bits must be zero and are not stored in the - instruction, giving a 21 bit signed byte offset. - - -- : BFD_RELOC_AARCH64_LD64_GOT_LO12_NC - Unsigned 12 bit byte offset for 64 bit load/store from the page of - the GOT entry for this symbol. Used in conjunction with - BFD_RELOC_AARCH64_ADR_GOTPAGE. - - -- : BFD_RELOC_AARCH64_LDST_LO12 - AArch64 unspecified load/store instruction, holding bits 0 to 11 - of the address. Used in conjunction with - BFD_RELOC_AARCH64_ADR_HI21_PCREL. - - -- : BFD_RELOC_AARCH64_LDST8_LO12 - AArch64 8-bit load/store instruction, holding bits 0 to 11 of the - address. Used in conjunction with - BFD_RELOC_AARCH64_ADR_HI21_PCREL. + -- : BFD_RELOC_AARCH64_CALL26 + AArch64 26 bit pc-relative unconditional branch and link. The + lowest two bits must be zero and are not stored in the instruction, + giving a 28 bit signed byte offset. -- : BFD_RELOC_AARCH64_LDST16_LO12 AArch64 16-bit load/store instruction, holding bits 0 to 11 of the @@ -6147,145 +6405,168 @@ attributes. address. Used in conjunction with BFD_RELOC_AARCH64_ADR_HI21_PCREL. - -- : BFD_RELOC_AARCH64_MOVW_G0 - AArch64 MOV[NZK] instruction with most significant bits 0 to 15 of - an unsigned address/value. + -- : BFD_RELOC_AARCH64_GOT_LD_PREL19 + AArch64 Load Literal instruction, holding a 19 bit PC relative word + offset of the global offset table entry for a symbol. The lowest + two bits must be zero and are not stored in the instruction, + giving a 21 bit signed byte offset. This relocation type requires + signed overflow checking. - -- : BFD_RELOC_AARCH64_MOVW_G0_S - AArch64 MOV[NZ] instruction with most significant bits 0 to 15 of - a signed value. Changes instruction to MOVZ or MOVN depending on - the value's sign. + -- : BFD_RELOC_AARCH64_ADR_GOT_PAGE + Get to the page base of the global offset table entry for a symbol + as part of an ADRP instruction using a 21 bit PC relative + value.Used in conjunction with BFD_RELOC_AARCH64_LD64_GOT_LO12_NC. - -- : BFD_RELOC_AARCH64_MOVW_G0_NC - AArch64 MOV[NZK] instruction with less significant bits 0 to 15 of - an address/value. No overflow checking. + -- : BFD_RELOC_AARCH64_LD64_GOT_LO12_NC + Unsigned 12 bit byte offset for 64 bit load/store from the page of + the GOT entry for this symbol. Used in conjunction with + BFD_RELOC_AARCH64_ADR_GOTPAGE. Valid in LP64 ABI only. - -- : BFD_RELOC_AARCH64_MOVW_G1 - AArch64 MOV[NZK] instruction with most significant bits 16 to 31 - of an unsigned address/value. + -- : BFD_RELOC_AARCH64_LD32_GOT_LO12_NC + Unsigned 12 bit byte offset for 32 bit load/store from the page of + the GOT entry for this symbol. Used in conjunction with + BFD_RELOC_AARCH64_ADR_GOTPAGE. Valid in ILP32 ABI only. - -- : BFD_RELOC_AARCH64_MOVW_G1_NC - AArch64 MOV[NZK] instruction with less significant bits 16 to 31 - of an address/value. No overflow checking. + -- : BFD_RELOC_AARCH64_TLSGD_ADR_PAGE21 + Get to the page base of the global offset table entry for a symbols + tls_index structure as part of an adrp instruction using a 21 bit + PC relative value. Used in conjunction with + BFD_RELOC_AARCH64_TLSGD_ADD_LO12_NC. - -- : BFD_RELOC_AARCH64_MOVW_G1_S - AArch64 MOV[NZ] instruction with most significant bits 16 to 31 of - a signed value. Changes instruction to MOVZ or MOVN depending on - the value's sign. + -- : BFD_RELOC_AARCH64_TLSGD_ADD_LO12_NC + Unsigned 12 bit byte offset to global offset table entry for a + symbols tls_index structure. Used in conjunction with + BFD_RELOC_AARCH64_TLSGD_ADR_PAGE21. - -- : BFD_RELOC_AARCH64_MOVW_G2 - AArch64 MOV[NZK] instruction with most significant bits 32 to 47 - of an unsigned address/value. + -- : BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G1 + AArch64 TLS INITIAL EXEC relocation. - -- : BFD_RELOC_AARCH64_MOVW_G2_NC - AArch64 MOV[NZK] instruction with less significant bits 32 to 47 - of an address/value. No overflow checking. + -- : BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G0_NC + AArch64 TLS INITIAL EXEC relocation. - -- : BFD_RELOC_AARCH64_MOVW_G2_S - AArch64 MOV[NZ] instruction with most significant bits 32 to 47 of - a signed value. Changes instruction to MOVZ or MOVN depending on - the value's sign. + -- : BFD_RELOC_AARCH64_TLSIE_ADR_GOTTPREL_PAGE21 + AArch64 TLS INITIAL EXEC relocation. - -- : BFD_RELOC_AARCH64_MOVW_G3 - AArch64 MOV[NZK] instruction with most signficant bits 48 to 64 of - a signed or unsigned address/value. + -- : BFD_RELOC_AARCH64_TLSIE_LD64_GOTTPREL_LO12_NC + AArch64 TLS INITIAL EXEC relocation. - -- : BFD_RELOC_AARCH64_TLSDESC - AArch64 TLS relocation. + -- : BFD_RELOC_AARCH64_TLSIE_LD32_GOTTPREL_LO12_NC + AArch64 TLS INITIAL EXEC relocation. - -- : BFD_RELOC_AARCH64_TLSDESC_ADD - AArch64 TLS DESC relocation. + -- : BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_PREL19 + AArch64 TLS INITIAL EXEC relocation. - -- : BFD_RELOC_AARCH64_TLSDESC_ADD_LO12_NC - AArch64 TLS DESC relocation. + -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G2 + AArch64 TLS LOCAL EXEC relocation. + + -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1 + AArch64 TLS LOCAL EXEC relocation. + + -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1_NC + AArch64 TLS LOCAL EXEC relocation. + + -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0 + AArch64 TLS LOCAL EXEC relocation. + + -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0_NC + AArch64 TLS LOCAL EXEC relocation. + + -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_HI12 + AArch64 TLS LOCAL EXEC relocation. - -- : BFD_RELOC_AARCH64_TLSDESC_ADR_PAGE + -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12 + AArch64 TLS LOCAL EXEC relocation. + + -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12_NC + AArch64 TLS LOCAL EXEC relocation. + + -- : BFD_RELOC_AARCH64_TLSDESC_LD_PREL19 AArch64 TLS DESC relocation. -- : BFD_RELOC_AARCH64_TLSDESC_ADR_PREL21 AArch64 TLS DESC relocation. - -- : BFD_RELOC_AARCH64_TLSDESC_CALL + -- : BFD_RELOC_AARCH64_TLSDESC_ADR_PAGE21 AArch64 TLS DESC relocation. -- : BFD_RELOC_AARCH64_TLSDESC_LD64_LO12_NC AArch64 TLS DESC relocation. - -- : BFD_RELOC_AARCH64_TLSDESC_LD64_PREL19 + -- : BFD_RELOC_AARCH64_TLSDESC_LD32_LO12_NC AArch64 TLS DESC relocation. - -- : BFD_RELOC_AARCH64_TLSDESC_LDR - AArch64 TLS DESC relocation. - - -- : BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC + -- : BFD_RELOC_AARCH64_TLSDESC_ADD_LO12_NC AArch64 TLS DESC relocation. -- : BFD_RELOC_AARCH64_TLSDESC_OFF_G1 AArch64 TLS DESC relocation. - -- : BFD_RELOC_AARCH64_TLSGD_ADD_LO12_NC - Unsigned 12 bit byte offset to global offset table entry for a - symbols tls_index structure. Used in conjunction with - BFD_RELOC_AARCH64_TLSGD_ADR_PAGE21. + -- : BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC + AArch64 TLS DESC relocation. - -- : BFD_RELOC_AARCH64_TLSGD_ADR_PAGE21 - Get to the page base of the global offset table entry for a symbols - tls_index structure as part of an adrp instruction using a 21 bit - PC relative value. Used in conjunction with - BFD_RELOC_AARCH64_TLSGD_ADD_LO12_NC. + -- : BFD_RELOC_AARCH64_TLSDESC_LDR + AArch64 TLS DESC relocation. - -- : BFD_RELOC_AARCH64_TLSIE_ADR_GOTTPREL_PAGE21 - AArch64 TLS INITIAL EXEC relocation. + -- : BFD_RELOC_AARCH64_TLSDESC_ADD + AArch64 TLS DESC relocation. - -- : BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_PREL19 - AArch64 TLS INITIAL EXEC relocation. + -- : BFD_RELOC_AARCH64_TLSDESC_CALL + AArch64 TLS DESC relocation. - -- : BFD_RELOC_AARCH64_TLSIE_LD64_GOTTPREL_LO12_NC - AArch64 TLS INITIAL EXEC relocation. + -- : BFD_RELOC_AARCH64_COPY + AArch64 TLS relocation. - -- : BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G0_NC - AArch64 TLS INITIAL EXEC relocation. + -- : BFD_RELOC_AARCH64_GLOB_DAT + AArch64 TLS relocation. - -- : BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G1 - AArch64 TLS INITIAL EXEC relocation. + -- : BFD_RELOC_AARCH64_JUMP_SLOT + AArch64 TLS relocation. - -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_HI12 - AArch64 TLS LOCAL EXEC relocation. + -- : BFD_RELOC_AARCH64_RELATIVE + AArch64 TLS relocation. - -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12 - AArch64 TLS LOCAL EXEC relocation. + -- : BFD_RELOC_AARCH64_TLS_DTPMOD + AArch64 TLS relocation. - -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12_NC - AArch64 TLS LOCAL EXEC relocation. + -- : BFD_RELOC_AARCH64_TLS_DTPREL + AArch64 TLS relocation. - -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0 - AArch64 TLS LOCAL EXEC relocation. + -- : BFD_RELOC_AARCH64_TLS_TPREL + AArch64 TLS relocation. - -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0_NC - AArch64 TLS LOCAL EXEC relocation. + -- : BFD_RELOC_AARCH64_TLSDESC + AArch64 TLS relocation. - -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1 - AArch64 TLS LOCAL EXEC relocation. + -- : BFD_RELOC_AARCH64_IRELATIVE + AArch64 support for STT_GNU_IFUNC. - -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1_NC - AArch64 TLS LOCAL EXEC relocation. + -- : BFD_RELOC_AARCH64_RELOC_END + AArch64 pseudo relocation code to mark the end of the AArch64 + relocation enumerators that have direct mapping to ELF reloc codes. + There are a few more enumerators after this one; those are mainly + used by the AArch64 assembler for the internal fixup or to select + one of the above enumerators. - -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G2 - AArch64 TLS LOCAL EXEC relocation. + -- : BFD_RELOC_AARCH64_GAS_INTERNAL_FIXUP + AArch64 pseudo relocation code to be used internally by the AArch64 + assembler and not (currently) written to any object files. - -- : BFD_RELOC_AARCH64_TLS_DTPMOD64 - AArch64 TLS relocation. + -- : BFD_RELOC_AARCH64_LDST_LO12 + AArch64 unspecified load/store instruction, holding bits 0 to 11 + of the address. Used in conjunction with + BFD_RELOC_AARCH64_ADR_HI21_PCREL. - -- : BFD_RELOC_AARCH64_TLS_DTPREL64 - AArch64 TLS relocation. + -- : BFD_RELOC_AARCH64_LD_GOT_LO12_NC + AArch64 pseudo relocation code to be used internally by the AArch64 + assembler and not (currently) written to any object files. - -- : BFD_RELOC_AARCH64_TLS_TPREL64 - AArch64 TLS relocation. + -- : BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_LO12_NC + AArch64 pseudo relocation code to be used internally by the AArch64 + assembler and not (currently) written to any object files. - -- : BFD_RELOC_AARCH64_TSTBR14 - AArch64 14 bit pc-relative test bit and branch. The lowest two - bits must be zero and are not stored in the instruction, giving a - 16 bit signed byte offset. + -- : BFD_RELOC_AARCH64_TLSDESC_LD_LO12_NC + AArch64 pseudo relocation code to be used internally by the AArch64 + assembler and not (currently) written to any object files. -- : BFD_RELOC_TILEPRO_COPY -- : BFD_RELOC_TILEPRO_GLOB_DAT @@ -7414,6 +7695,10 @@ i960 KB, and 68020 and 68030 for Motorola 68020 and 68030. bfd_arch_k1om, /* Intel K1OM */ #define bfd_mach_k1om (1 << 6) #define bfd_mach_k1om_intel_syntax (bfd_mach_k1om | bfd_mach_i386_intel_syntax) + #define bfd_mach_i386_nacl (1 << 7) + #define bfd_mach_i386_i386_nacl (bfd_mach_i386_i386 | bfd_mach_i386_nacl) + #define bfd_mach_x86_64_nacl (bfd_mach_x86_64 | bfd_mach_i386_nacl) + #define bfd_mach_x64_32_nacl (bfd_mach_x64_32 | bfd_mach_i386_nacl) bfd_arch_we32k, /* AT&T WE32xxx */ bfd_arch_tahoe, /* CCI/Harris Tahoe */ bfd_arch_i860, /* Intel 860 */ @@ -7528,6 +7813,12 @@ i960 KB, and 68020 and 68030 for Motorola 68020 and 68030. #define bfd_mach_arm_ep9312 11 #define bfd_mach_arm_iWMMXt 12 #define bfd_mach_arm_iWMMXt2 13 + bfd_arch_nds32, /* Andes NDS32 */ + #define bfd_mach_n1 1 + #define bfd_mach_n1h 2 + #define bfd_mach_n1h_v2 3 + #define bfd_mach_n1h_v3 4 + #define bfd_mach_n1h_v3m 5 bfd_arch_ns32k, /* National Semiconductors ns32000 */ bfd_arch_w65, /* WDC 65816 */ bfd_arch_tic30, /* Texas Instruments TMS320C30 */ @@ -7651,7 +7942,12 @@ i960 KB, and 68020 and 68030 for Motorola 68020 and 68030. #define bfd_mach_msp14 14 #define bfd_mach_msp15 15 #define bfd_mach_msp16 16 + #define bfd_mach_msp20 20 #define bfd_mach_msp21 21 + #define bfd_mach_msp22 22 + #define bfd_mach_msp23 23 + #define bfd_mach_msp24 24 + #define bfd_mach_msp26 26 #define bfd_mach_msp31 31 #define bfd_mach_msp32 32 #define bfd_mach_msp33 33 @@ -7659,6 +7955,10 @@ i960 KB, and 68020 and 68030 for Motorola 68020 and 68030. #define bfd_mach_msp42 42 #define bfd_mach_msp43 43 #define bfd_mach_msp44 44 + #define bfd_mach_msp430x 45 + #define bfd_mach_msp46 46 + #define bfd_mach_msp47 47 + #define bfd_mach_msp54 54 bfd_arch_xc16x, /* Infineon's XC16X Series. */ #define bfd_mach_xc16x 1 #define bfd_mach_xc16xl 2 @@ -7682,6 +7982,7 @@ i960 KB, and 68020 and 68030 for Motorola 68020 and 68030. #define bfd_mach_tilegx32 2 bfd_arch_aarch64, /* AArch64 */ #define bfd_mach_aarch64 0 + #define bfd_mach_aarch64_ilp32 32 bfd_arch_nios2, #define bfd_mach_nios2 0 bfd_arch_last @@ -7943,6 +8244,9 @@ error. On error, FD is always closed. + A copy of the FILENAME argument is stored in the newly created BFD. +It can be accessed via the bfd_get_filename() macro. + 2.14.1.2 `bfd_openr' .................... @@ -7959,6 +8263,9 @@ function. are `bfd_error_no_memory', `bfd_error_invalid_target' or `system_call' error. + A copy of the FILENAME argument is stored in the newly created BFD. +It can be accessed via the bfd_get_filename() macro. + 2.14.1.3 `bfd_fdopenr' ...................... @@ -7982,15 +8289,21 @@ operations on other files. On error, FD is closed. + A copy of the FILENAME argument is stored in the newly created BFD. +It can be accessed via the bfd_get_filename() macro. + 2.14.1.4 `bfd_openstreamr' .......................... *Synopsis* - bfd *bfd_openstreamr (const char *, const char *, void *); + bfd *bfd_openstreamr (const char * filename, const char * target, void * stream); *Description* Open a BFD for read access on an existing stdio stream. When the BFD is passed to `bfd_close', the stream will be closed. + A copy of the FILENAME argument is stored in the newly created BFD. +It can be accessed via the bfd_get_filename() macro. + 2.14.1.5 `bfd_openr_iovec' .......................... @@ -8039,6 +8352,9 @@ or returns -1 on failure (setting `bfd_error'). Possible errors are `bfd_error_no_memory', `bfd_error_invalid_target' and `bfd_error_system_call'. + A copy of the FILENAME argument is stored in the newly created BFD. +It can be accessed via the bfd_get_filename() macro. + 2.14.1.6 `bfd_openw' .................... @@ -8051,6 +8367,9 @@ TARGET, and return a pointer to it. Possible errors are `bfd_error_system_call', `bfd_error_no_memory', `bfd_error_invalid_target'. + A copy of the FILENAME argument is stored in the newly created BFD. +It can be accessed via the bfd_get_filename() macro. + 2.14.1.7 `bfd_close' .................... @@ -8098,6 +8417,9 @@ Create a new BFD in the manner of `bfd_openw', but without opening a file. The new BFD takes the target from the target used by TEMPL. The format is always set to `bfd_object'. + A copy of the FILENAME argument is stored in the newly created BFD. +It can be accessed via the bfd_get_filename() macro. + 2.14.1.10 `bfd_make_writable' ............................. @@ -8182,12 +8504,26 @@ Return the updated CRC32 value. *Synopsis* char *bfd_get_debug_link_info (bfd *abfd, unsigned long *crc32_out); *Description* -fetch the filename and CRC32 value for any separate debuginfo -associated with ABFD. Return NULL if no such info found, otherwise +Fetch the filename and CRC32 value for any separate debuginfo +associated with ABFD. Return NULL if no such info found, otherwise return filename and update CRC32_OUT. The returned filename is allocated with `malloc'; freeing it is the responsibility of the caller. -2.14.1.18 `separate_debug_file_exists' +2.14.1.18 `bfd_get_alt_debug_link_info' +....................................... + +*Synopsis* + char *bfd_get_alt_debug_link_info (bfd * abfd, + bfd_size_type *buildid_len, + bfd_byte **buildid_out); + *Description* +Fetch the filename and BuildID value for any alternate debuginfo +associated with ABFD. Return NULL if no such info found, otherwise +return filename and update BUILDID_LEN and BUILDID_OUT. The returned +filename and build_id are allocated with `malloc'; freeing them is the +responsibility of the caller. + +2.14.1.19 `separate_debug_file_exists' ...................................... *Synopsis* @@ -8196,19 +8532,30 @@ allocated with `malloc'; freeing it is the responsibility of the caller. *Description* Checks to see if NAME is a file and if its contents match CRC32. -2.14.1.19 `find_separate_debug_file' +2.14.1.20 `separate_alt_debug_file_exists' +.......................................... + +*Synopsis* + bfd_boolean separate_alt_debug_file_exists + (char *name, unsigned long crc32); + *Description* +Checks to see if NAME is a file and if its BuildID matches BUILDID. + +2.14.1.21 `find_separate_debug_file' .................................... *Synopsis* char *find_separate_debug_file (bfd *abfd); *Description* -Searches ABFD for a reference to separate debugging information, scans -various locations in the filesystem, including the file tree rooted at -DEBUG_FILE_DIRECTORY, and returns a filename of such debugging -information if the file is found and has matching CRC32. Returns NULL -if no reference to debugging file exists, or file cannot be found. +Searches ABFD for a section called SECTION_NAME which is expected to +contain a reference to a file containing separate debugging +information. The function scans various locations in the filesystem, +including the file tree rooted at DEBUG_FILE_DIRECTORY, and returns the +first matching filename that it finds. If CHECK_CRC is TRUE then the +contents of the file must also match the CRC value contained in +SECTION_NAME. Returns NULL if no valid file could be found. -2.14.1.20 `bfd_follow_gnu_debuglink' +2.14.1.22 `bfd_follow_gnu_debuglink' .................................... *Synopsis* @@ -8229,7 +8576,27 @@ at build time. [XXX this feature is not currently implemented]. pointer to a heap-allocated string containing the filename. The caller is responsible for freeing this string. -2.14.1.21 `bfd_create_gnu_debuglink_section' +2.14.1.23 `bfd_follow_gnu_debugaltlink' +....................................... + +*Synopsis* + char *bfd_follow_gnu_debugaltlink (bfd *abfd, const char *dir); + *Description* +Takes a BFD and searches it for a .gnu_debugaltlink section. If this +section is found, it examines the section for the name of a file +containing auxiliary debugging information. It then searches the +filesystem for this file in a set of standard locations, including the +directory tree rooted at DIR, and if found returns the full filename. + + If DIR is NULL, it will search a default path configured into libbfd +at build time. [FIXME: This feature is not currently implemented]. + + *Returns* +`NULL' on any errors or failure to locate the debug file, otherwise a +pointer to a heap-allocated string containing the filename. The caller +is responsible for freeing this string. + +2.14.1.24 `bfd_create_gnu_debuglink_section' ............................................ *Synopsis* @@ -8243,7 +8610,7 @@ sized to be big enough to contain a link to the specified FILENAME. A pointer to the new section is returned if all is ok. Otherwise `NULL' is returned and bfd_error is set. -2.14.1.22 `bfd_fill_in_gnu_debuglink_section' +2.14.1.25 `bfd_fill_in_gnu_debuglink_section' ............................................. *Synopsis* @@ -8258,20 +8625,6 @@ FILENAME. The filename should be relative to the current directory. `TRUE' is returned if all is ok. Otherwise `FALSE' is returned and bfd_error is set. -2.14.1.23 `bfd_extract_object_only_section' -........................................... - -*Synopsis* - const char *bfd_extract_object_only_section - (bfd *abfd); - *Description* -Takes a ABFD and extract the .gnu_object_only section into a temporary -file. - - *Returns* -The name of the temporary file is returned if all is ok. Otherwise -`NULL' is returned and bfd_error is set. - File: bfd.info, Node: Internal, Next: File Caching, Prev: Opening and Closing, Up: BFD front end @@ -8455,7 +8808,7 @@ The file caching mechanism is embedded within BFD and allows the application to open as many BFDs as it wants without regard to the underlying operating system's file descriptor limit (often as low as 20 open files). The module in `cache.c' maintains a least recently used -list of `BFD_CACHE_MAX_OPEN' files, and exports the name +list of `bfd_cache_max_open' files, and exports the name `bfd_cache_lookup', which runs around and makes sure that the required BFD is open. If not, then it chooses a file to close, closes it and opens the one wanted, returning its file handle. @@ -10919,41 +11272,41 @@ BFD Index * BFD: Overview. (line 6) * BFD canonical format: Canonical format. (line 11) * bfd_alloc: Opening and Closing. - (line 218) + (line 239) * bfd_alloc2: Opening and Closing. - (line 227) + (line 248) * bfd_alt_mach_code: Miscellaneous. (line 308) -* bfd_arch_bits_per_address: Architectures. (line 570) -* bfd_arch_bits_per_byte: Architectures. (line 562) -* bfd_arch_default_fill: Architectures. (line 651) -* bfd_arch_get_compatible: Architectures. (line 505) -* bfd_arch_list: Architectures. (line 496) -* bfd_arch_mach_octets_per_byte: Architectures. (line 639) -* BFD_ARELOC_BFIN_ADD: howto manager. (line 1111) -* BFD_ARELOC_BFIN_ADDR: howto manager. (line 1162) -* BFD_ARELOC_BFIN_AND: howto manager. (line 1132) -* BFD_ARELOC_BFIN_COMP: howto manager. (line 1153) -* BFD_ARELOC_BFIN_CONST: howto manager. (line 1108) -* BFD_ARELOC_BFIN_DIV: howto manager. (line 1120) -* BFD_ARELOC_BFIN_HWPAGE: howto manager. (line 1159) -* BFD_ARELOC_BFIN_LAND: howto manager. (line 1141) -* BFD_ARELOC_BFIN_LEN: howto manager. (line 1147) -* BFD_ARELOC_BFIN_LOR: howto manager. (line 1144) -* BFD_ARELOC_BFIN_LSHIFT: howto manager. (line 1126) -* BFD_ARELOC_BFIN_MOD: howto manager. (line 1123) -* BFD_ARELOC_BFIN_MULT: howto manager. (line 1117) -* BFD_ARELOC_BFIN_NEG: howto manager. (line 1150) -* BFD_ARELOC_BFIN_OR: howto manager. (line 1135) -* BFD_ARELOC_BFIN_PAGE: howto manager. (line 1156) -* BFD_ARELOC_BFIN_PUSH: howto manager. (line 1105) -* BFD_ARELOC_BFIN_RSHIFT: howto manager. (line 1129) -* BFD_ARELOC_BFIN_SUB: howto manager. (line 1114) -* BFD_ARELOC_BFIN_XOR: howto manager. (line 1138) +* bfd_arch_bits_per_address: Architectures. (line 590) +* bfd_arch_bits_per_byte: Architectures. (line 582) +* bfd_arch_default_fill: Architectures. (line 671) +* bfd_arch_get_compatible: Architectures. (line 525) +* bfd_arch_list: Architectures. (line 516) +* bfd_arch_mach_octets_per_byte: Architectures. (line 659) +* BFD_ARELOC_BFIN_ADD: howto manager. (line 1120) +* BFD_ARELOC_BFIN_ADDR: howto manager. (line 1171) +* BFD_ARELOC_BFIN_AND: howto manager. (line 1141) +* BFD_ARELOC_BFIN_COMP: howto manager. (line 1162) +* BFD_ARELOC_BFIN_CONST: howto manager. (line 1117) +* BFD_ARELOC_BFIN_DIV: howto manager. (line 1129) +* BFD_ARELOC_BFIN_HWPAGE: howto manager. (line 1168) +* BFD_ARELOC_BFIN_LAND: howto manager. (line 1150) +* BFD_ARELOC_BFIN_LEN: howto manager. (line 1156) +* BFD_ARELOC_BFIN_LOR: howto manager. (line 1153) +* BFD_ARELOC_BFIN_LSHIFT: howto manager. (line 1135) +* BFD_ARELOC_BFIN_MOD: howto manager. (line 1132) +* BFD_ARELOC_BFIN_MULT: howto manager. (line 1126) +* BFD_ARELOC_BFIN_NEG: howto manager. (line 1159) +* BFD_ARELOC_BFIN_OR: howto manager. (line 1144) +* BFD_ARELOC_BFIN_PAGE: howto manager. (line 1165) +* BFD_ARELOC_BFIN_PUSH: howto manager. (line 1114) +* BFD_ARELOC_BFIN_RSHIFT: howto manager. (line 1138) +* BFD_ARELOC_BFIN_SUB: howto manager. (line 1123) +* BFD_ARELOC_BFIN_XOR: howto manager. (line 1147) * bfd_cache_close: File Caching. (line 26) * bfd_cache_close_all: File Caching. (line 39) * bfd_cache_init: File Caching. (line 18) * bfd_calc_gnu_debuglink_crc32: Opening and Closing. - (line 254) + (line 275) * bfd_canonicalize_reloc: Miscellaneous. (line 19) * bfd_canonicalize_symtab: symbol handling functions. (line 50) @@ -10961,9 +11314,9 @@ BFD Index * bfd_check_format_matches: Formats. (line 52) * bfd_check_overflow: typedef arelent. (line 348) * bfd_close: Opening and Closing. - (line 143) -* bfd_close_all_done: Opening and Closing. (line 161) +* bfd_close_all_done: Opening and Closing. + (line 179) * bfd_coff_backend_data: coff. (line 305) * bfd_copy_private_bfd_data: Miscellaneous. (line 158) * bfd_copy_private_header_data: Miscellaneous. (line 140) @@ -10974,60 +11327,62 @@ BFD Index * bfd_core_file_failing_signal: Core Files. (line 21) * bfd_core_file_pid: Core Files. (line 30) * bfd_create: Opening and Closing. - (line 180) + (line 198) * bfd_create_gnu_debuglink_section: Opening and Closing. - (line 321) + (line 387) * bfd_decode_symclass: symbol handling functions. (line 111) -* bfd_default_arch_struct: Architectures. (line 517) -* bfd_default_compatible: Architectures. (line 579) -* bfd_default_reloc_type_lookup: howto manager. (line 3165) -* bfd_default_scan: Architectures. (line 588) -* bfd_default_set_arch_mach: Architectures. (line 535) +* bfd_default_arch_struct: Architectures. (line 537) +* bfd_default_compatible: Architectures. (line 599) +* bfd_default_reloc_type_lookup: howto manager. (line 3441) +* bfd_default_scan: Architectures. (line 608) +* bfd_default_set_arch_mach: Architectures. (line 555) * bfd_demangle: Miscellaneous. (line 359) * bfd_emul_get_commonpagesize: Miscellaneous. (line 339) * bfd_emul_get_maxpagesize: Miscellaneous. (line 319) * bfd_emul_set_commonpagesize: Miscellaneous. (line 350) * bfd_emul_set_maxpagesize: Miscellaneous. (line 330) * bfd_errmsg: Error reporting. (line 67) -* bfd_extract_object_only_section: Opening and Closing. - (line 350) * bfd_fdopenr: Opening and Closing. - (line 51) + (line 57) * bfd_fill_in_gnu_debuglink_section: Opening and Closing. - (line 335) + (line 401) * bfd_find_target: bfd_target. (line 473) * bfd_find_version_for_sym: Writing the symbol table. (line 81) +* bfd_follow_gnu_debugaltlink: Opening and Closing. + (line 367) * bfd_follow_gnu_debuglink: Opening and Closing. - (line 300) + (line 346) * bfd_fopen: Opening and Closing. (line 12) * bfd_format_string: Formats. (line 79) * bfd_generic_define_common_symbol: Writing the symbol table. (line 68) * bfd_generic_discard_group: section prototypes. (line 304) -* bfd_generic_gc_sections: howto manager. (line 3196) -* bfd_generic_get_relocated_section_contents: howto manager. (line 3226) +* bfd_generic_gc_sections: howto manager. (line 3472) +* bfd_generic_get_relocated_section_contents: howto manager. (line 3502) * bfd_generic_is_group_section: section prototypes. (line 296) -* bfd_generic_lookup_section_flags: howto manager. (line 3206) -* bfd_generic_merge_sections: howto manager. (line 3216) -* bfd_generic_relax_section: howto manager. (line 3183) -* bfd_get_arch: Architectures. (line 546) -* bfd_get_arch_info: Architectures. (line 598) +* bfd_generic_lookup_section_flags: howto manager. (line 3482) +* bfd_generic_merge_sections: howto manager. (line 3492) +* bfd_generic_relax_section: howto manager. (line 3459) +* bfd_get_alt_debug_link_info: Opening and Closing. + (line 300) +* bfd_get_arch: Architectures. (line 566) +* bfd_get_arch_info: Architectures. (line 618) * bfd_get_arch_size: Miscellaneous. (line 63) * bfd_get_assert_handler: Error reporting. (line 150) * bfd_get_debug_link_info: Opening and Closing. - (line 268) + (line 289) * bfd_get_error: Error reporting. (line 48) * bfd_get_error_handler: Error reporting. (line 118) * bfd_get_gp_size: Miscellaneous. (line 104) * bfd_get_linker_section: section prototypes. (line 36) -* bfd_get_mach: Architectures. (line 554) -* bfd_get_mtime: Miscellaneous. (line 418) +* bfd_get_mach: Architectures. (line 574) +* bfd_get_mtime: Miscellaneous. (line 410) * bfd_get_next_mapent: Archives. (line 58) * bfd_get_next_section_by_name: section prototypes. (line 26) -* bfd_get_reloc_code_name: howto manager. (line 3174) +* bfd_get_reloc_code_name: howto manager. (line 3450) * bfd_get_reloc_size: typedef arelent. (line 327) * bfd_get_reloc_upper_bound: Miscellaneous. (line 9) * bfd_get_section_by_name: section prototypes. (line 17) @@ -11035,12 +11390,11 @@ BFD Index * bfd_get_section_contents: section prototypes. (line 251) * bfd_get_sign_extend_vma: Miscellaneous. (line 76) * bfd_get_size <1>: Internal. (line 25) -* bfd_get_size: Miscellaneous. (line 427) +* bfd_get_size: Miscellaneous. (line 419) * bfd_get_symtab_upper_bound: symbol handling functions. (line 6) * bfd_get_target_info: bfd_target. (line 489) * bfd_get_unique_section_name: section prototypes. (line 64) -* bfd_group_signature: Miscellaneous. (line 370) * bfd_h_put_size: Internal. (line 97) * bfd_hash_allocate: Creating and Freeing a Hash Table. (line 17) @@ -11073,41 +11427,41 @@ BFD Index * bfd_link_split_section: Writing the symbol table. (line 44) * bfd_log2: Internal. (line 164) -* bfd_lookup_arch: Architectures. (line 606) +* bfd_lookup_arch: Architectures. (line 626) * bfd_make_debug_symbol: symbol handling functions. (line 102) * bfd_make_empty_symbol: symbol handling functions. (line 78) * bfd_make_readable: Opening and Closing. - (line 204) + (line 225) * bfd_make_section: section prototypes. (line 143) * bfd_make_section_anyway: section prototypes. (line 114) * bfd_make_section_anyway_with_flags: section prototypes. (line 96) * bfd_make_section_old_way: section prototypes. (line 76) * bfd_make_section_with_flags: section prototypes. (line 130) * bfd_make_writable: Opening and Closing. - (line 190) + (line 211) * bfd_malloc_and_get_section: section prototypes. (line 268) * bfd_map_over_sections: section prototypes. (line 178) * bfd_merge_private_bfd_data: Miscellaneous. (line 174) -* bfd_mmap: Miscellaneous. (line 456) -* bfd_octets_per_byte: Architectures. (line 629) +* bfd_mmap: Miscellaneous. (line 448) +* bfd_octets_per_byte: Architectures. (line 649) * bfd_open_file: File Caching. (line 52) * bfd_openr: Opening and Closing. - (line 35) + (line 38) * bfd_openr_iovec: Opening and Closing. - (line 83) + (line 95) * bfd_openr_next_archived_file: Archives. (line 84) * bfd_openstreamr: Opening and Closing. - (line 74) + (line 83) * bfd_openw: Opening and Closing. - (line 131) + (line 146) * bfd_perform_relocation: typedef arelent. (line 364) * bfd_perror: Error reporting. (line 76) * bfd_print_symbol_vandf: symbol handling functions. (line 70) -* bfd_printable_arch_mach: Architectures. (line 617) -* bfd_printable_name: Architectures. (line 477) +* bfd_printable_arch_mach: Architectures. (line 637) +* bfd_printable_name: Architectures. (line 497) * bfd_put_size: Internal. (line 22) * BFD_RELOC_12_PCREL: howto manager. (line 39) * BFD_RELOC_14: howto manager. (line 31) @@ -11119,46 +11473,46 @@ BFD Index * BFD_RELOC_16_PCREL_S2: howto manager. (line 111) * BFD_RELOC_16_PLT_PCREL: howto manager. (line 63) * BFD_RELOC_16_PLTOFF: howto manager. (line 67) -* BFD_RELOC_16C_ABS20: howto manager. (line 2215) -* BFD_RELOC_16C_ABS20_C: howto manager. (line 2216) -* BFD_RELOC_16C_ABS24: howto manager. (line 2217) -* BFD_RELOC_16C_ABS24_C: howto manager. (line 2218) -* BFD_RELOC_16C_DISP04: howto manager. (line 2195) -* BFD_RELOC_16C_DISP04_C: howto manager. (line 2196) -* BFD_RELOC_16C_DISP08: howto manager. (line 2197) -* BFD_RELOC_16C_DISP08_C: howto manager. (line 2198) -* BFD_RELOC_16C_DISP16: howto manager. (line 2199) -* BFD_RELOC_16C_DISP16_C: howto manager. (line 2200) -* BFD_RELOC_16C_DISP24: howto manager. (line 2201) -* BFD_RELOC_16C_DISP24_C: howto manager. (line 2202) -* BFD_RELOC_16C_DISP24a: howto manager. (line 2203) -* BFD_RELOC_16C_DISP24a_C: howto manager. (line 2204) -* BFD_RELOC_16C_IMM04: howto manager. (line 2219) -* BFD_RELOC_16C_IMM04_C: howto manager. (line 2220) -* BFD_RELOC_16C_IMM16: howto manager. (line 2221) -* BFD_RELOC_16C_IMM16_C: howto manager. (line 2222) -* BFD_RELOC_16C_IMM20: howto manager. (line 2223) -* BFD_RELOC_16C_IMM20_C: howto manager. (line 2224) -* BFD_RELOC_16C_IMM24: howto manager. (line 2225) -* BFD_RELOC_16C_IMM24_C: howto manager. (line 2226) -* BFD_RELOC_16C_IMM32: howto manager. (line 2227) -* BFD_RELOC_16C_IMM32_C: howto manager. (line 2228) -* BFD_RELOC_16C_NUM08: howto manager. (line 2189) -* BFD_RELOC_16C_NUM08_C: howto manager. (line 2190) -* BFD_RELOC_16C_NUM16: howto manager. (line 2191) -* BFD_RELOC_16C_NUM16_C: howto manager. (line 2192) -* BFD_RELOC_16C_NUM32: howto manager. (line 2193) -* BFD_RELOC_16C_NUM32_C: howto manager. (line 2194) -* BFD_RELOC_16C_REG04: howto manager. (line 2205) -* BFD_RELOC_16C_REG04_C: howto manager. (line 2206) -* BFD_RELOC_16C_REG04a: howto manager. (line 2207) -* BFD_RELOC_16C_REG04a_C: howto manager. (line 2208) -* BFD_RELOC_16C_REG14: howto manager. (line 2209) -* BFD_RELOC_16C_REG14_C: howto manager. (line 2210) -* BFD_RELOC_16C_REG16: howto manager. (line 2211) -* BFD_RELOC_16C_REG16_C: howto manager. (line 2212) -* BFD_RELOC_16C_REG20: howto manager. (line 2213) -* BFD_RELOC_16C_REG20_C: howto manager. (line 2214) +* BFD_RELOC_16C_ABS20: howto manager. (line 2409) +* BFD_RELOC_16C_ABS20_C: howto manager. (line 2410) +* BFD_RELOC_16C_ABS24: howto manager. (line 2411) +* BFD_RELOC_16C_ABS24_C: howto manager. (line 2412) +* BFD_RELOC_16C_DISP04: howto manager. (line 2389) +* BFD_RELOC_16C_DISP04_C: howto manager. (line 2390) +* BFD_RELOC_16C_DISP08: howto manager. (line 2391) +* BFD_RELOC_16C_DISP08_C: howto manager. (line 2392) +* BFD_RELOC_16C_DISP16: howto manager. (line 2393) +* BFD_RELOC_16C_DISP16_C: howto manager. (line 2394) +* BFD_RELOC_16C_DISP24: howto manager. (line 2395) +* BFD_RELOC_16C_DISP24_C: howto manager. (line 2396) +* BFD_RELOC_16C_DISP24a: howto manager. (line 2397) +* BFD_RELOC_16C_DISP24a_C: howto manager. (line 2398) +* BFD_RELOC_16C_IMM04: howto manager. (line 2413) +* BFD_RELOC_16C_IMM04_C: howto manager. (line 2414) +* BFD_RELOC_16C_IMM16: howto manager. (line 2415) +* BFD_RELOC_16C_IMM16_C: howto manager. (line 2416) +* BFD_RELOC_16C_IMM20: howto manager. (line 2417) +* BFD_RELOC_16C_IMM20_C: howto manager. (line 2418) +* BFD_RELOC_16C_IMM24: howto manager. (line 2419) +* BFD_RELOC_16C_IMM24_C: howto manager. (line 2420) +* BFD_RELOC_16C_IMM32: howto manager. (line 2421) +* BFD_RELOC_16C_IMM32_C: howto manager. (line 2422) +* BFD_RELOC_16C_NUM08: howto manager. (line 2383) +* BFD_RELOC_16C_NUM08_C: howto manager. (line 2384) +* BFD_RELOC_16C_NUM16: howto manager. (line 2385) +* BFD_RELOC_16C_NUM16_C: howto manager. (line 2386) +* BFD_RELOC_16C_NUM32: howto manager. (line 2387) +* BFD_RELOC_16C_NUM32_C: howto manager. (line 2388) +* BFD_RELOC_16C_REG04: howto manager. (line 2399) +* BFD_RELOC_16C_REG04_C: howto manager. (line 2400) +* BFD_RELOC_16C_REG04a: howto manager. (line 2401) +* BFD_RELOC_16C_REG04a_C: howto manager. (line 2402) +* BFD_RELOC_16C_REG14: howto manager. (line 2403) +* BFD_RELOC_16C_REG14_C: howto manager. (line 2404) +* BFD_RELOC_16C_REG16: howto manager. (line 2405) +* BFD_RELOC_16C_REG16_C: howto manager. (line 2406) +* BFD_RELOC_16C_REG20: howto manager. (line 2407) +* BFD_RELOC_16C_REG20_C: howto manager. (line 2408) * BFD_RELOC_23_PCREL_S2: howto manager. (line 112) * BFD_RELOC_24: howto manager. (line 29) * BFD_RELOC_24_PCREL: howto manager. (line 37) @@ -11173,81 +11527,85 @@ BFD Index * BFD_RELOC_32_PLT_PCREL: howto manager. (line 61) * BFD_RELOC_32_PLTOFF: howto manager. (line 66) * BFD_RELOC_32_SECREL: howto manager. (line 48) -* BFD_RELOC_386_COPY: howto manager. (line 576) -* BFD_RELOC_386_GLOB_DAT: howto manager. (line 577) -* BFD_RELOC_386_GOT32: howto manager. (line 574) -* BFD_RELOC_386_GOTOFF: howto manager. (line 580) -* BFD_RELOC_386_GOTPC: howto manager. (line 581) -* BFD_RELOC_386_IRELATIVE: howto manager. (line 597) -* BFD_RELOC_386_JUMP_SLOT: howto manager. (line 578) -* BFD_RELOC_386_PLT32: howto manager. (line 575) -* BFD_RELOC_386_RELATIVE: howto manager. (line 579) -* BFD_RELOC_386_TLS_DESC: howto manager. (line 596) -* BFD_RELOC_386_TLS_DESC_CALL: howto manager. (line 595) -* BFD_RELOC_386_TLS_DTPMOD32: howto manager. (line 591) -* BFD_RELOC_386_TLS_DTPOFF32: howto manager. (line 592) -* BFD_RELOC_386_TLS_GD: howto manager. (line 586) -* BFD_RELOC_386_TLS_GOTDESC: howto manager. (line 594) -* BFD_RELOC_386_TLS_GOTIE: howto manager. (line 584) -* BFD_RELOC_386_TLS_IE: howto manager. (line 583) -* BFD_RELOC_386_TLS_IE_32: howto manager. (line 589) -* BFD_RELOC_386_TLS_LDM: howto manager. (line 587) -* BFD_RELOC_386_TLS_LDO_32: howto manager. (line 588) -* BFD_RELOC_386_TLS_LE: howto manager. (line 585) -* BFD_RELOC_386_TLS_LE_32: howto manager. (line 590) -* BFD_RELOC_386_TLS_TPOFF: howto manager. (line 582) -* BFD_RELOC_386_TLS_TPOFF32: howto manager. (line 593) -* BFD_RELOC_390_12: howto manager. (line 1810) -* BFD_RELOC_390_20: howto manager. (line 1910) -* BFD_RELOC_390_COPY: howto manager. (line 1819) -* BFD_RELOC_390_GLOB_DAT: howto manager. (line 1822) -* BFD_RELOC_390_GOT12: howto manager. (line 1813) -* BFD_RELOC_390_GOT16: howto manager. (line 1834) -* BFD_RELOC_390_GOT20: howto manager. (line 1911) -* BFD_RELOC_390_GOT64: howto manager. (line 1852) -* BFD_RELOC_390_GOTENT: howto manager. (line 1858) -* BFD_RELOC_390_GOTOFF64: howto manager. (line 1861) -* BFD_RELOC_390_GOTPC: howto manager. (line 1831) -* BFD_RELOC_390_GOTPCDBL: howto manager. (line 1849) -* BFD_RELOC_390_GOTPLT12: howto manager. (line 1864) -* BFD_RELOC_390_GOTPLT16: howto manager. (line 1867) -* BFD_RELOC_390_GOTPLT20: howto manager. (line 1912) -* BFD_RELOC_390_GOTPLT32: howto manager. (line 1870) -* BFD_RELOC_390_GOTPLT64: howto manager. (line 1873) -* BFD_RELOC_390_GOTPLTENT: howto manager. (line 1876) -* BFD_RELOC_390_IRELATIVE: howto manager. (line 1916) -* BFD_RELOC_390_JMP_SLOT: howto manager. (line 1825) -* BFD_RELOC_390_PC16DBL: howto manager. (line 1837) -* BFD_RELOC_390_PC32DBL: howto manager. (line 1843) -* BFD_RELOC_390_PLT16DBL: howto manager. (line 1840) -* BFD_RELOC_390_PLT32: howto manager. (line 1816) -* BFD_RELOC_390_PLT32DBL: howto manager. (line 1846) -* BFD_RELOC_390_PLT64: howto manager. (line 1855) -* BFD_RELOC_390_PLTOFF16: howto manager. (line 1879) -* BFD_RELOC_390_PLTOFF32: howto manager. (line 1882) -* BFD_RELOC_390_PLTOFF64: howto manager. (line 1885) -* BFD_RELOC_390_RELATIVE: howto manager. (line 1828) -* BFD_RELOC_390_TLS_DTPMOD: howto manager. (line 1905) -* BFD_RELOC_390_TLS_DTPOFF: howto manager. (line 1906) -* BFD_RELOC_390_TLS_GD32: howto manager. (line 1891) -* BFD_RELOC_390_TLS_GD64: howto manager. (line 1892) -* BFD_RELOC_390_TLS_GDCALL: howto manager. (line 1889) -* BFD_RELOC_390_TLS_GOTIE12: howto manager. (line 1893) -* BFD_RELOC_390_TLS_GOTIE20: howto manager. (line 1913) -* BFD_RELOC_390_TLS_GOTIE32: howto manager. (line 1894) -* BFD_RELOC_390_TLS_GOTIE64: howto manager. (line 1895) -* BFD_RELOC_390_TLS_IE32: howto manager. (line 1898) -* BFD_RELOC_390_TLS_IE64: howto manager. (line 1899) -* BFD_RELOC_390_TLS_IEENT: howto manager. (line 1900) -* BFD_RELOC_390_TLS_LDCALL: howto manager. (line 1890) -* BFD_RELOC_390_TLS_LDM32: howto manager. (line 1896) -* BFD_RELOC_390_TLS_LDM64: howto manager. (line 1897) -* BFD_RELOC_390_TLS_LDO32: howto manager. (line 1903) -* BFD_RELOC_390_TLS_LDO64: howto manager. (line 1904) -* BFD_RELOC_390_TLS_LE32: howto manager. (line 1901) -* BFD_RELOC_390_TLS_LE64: howto manager. (line 1902) -* BFD_RELOC_390_TLS_LOAD: howto manager. (line 1888) -* BFD_RELOC_390_TLS_TPOFF: howto manager. (line 1907) +* BFD_RELOC_386_COPY: howto manager. (line 577) +* BFD_RELOC_386_GLOB_DAT: howto manager. (line 578) +* BFD_RELOC_386_GOT32: howto manager. (line 575) +* BFD_RELOC_386_GOTOFF: howto manager. (line 581) +* BFD_RELOC_386_GOTPC: howto manager. (line 582) +* BFD_RELOC_386_IRELATIVE: howto manager. (line 598) +* BFD_RELOC_386_JUMP_SLOT: howto manager. (line 579) +* BFD_RELOC_386_PLT32: howto manager. (line 576) +* BFD_RELOC_386_RELATIVE: howto manager. (line 580) +* BFD_RELOC_386_TLS_DESC: howto manager. (line 597) +* BFD_RELOC_386_TLS_DESC_CALL: howto manager. (line 596) +* BFD_RELOC_386_TLS_DTPMOD32: howto manager. (line 592) +* BFD_RELOC_386_TLS_DTPOFF32: howto manager. (line 593) +* BFD_RELOC_386_TLS_GD: howto manager. (line 587) +* BFD_RELOC_386_TLS_GOTDESC: howto manager. (line 595) +* BFD_RELOC_386_TLS_GOTIE: howto manager. (line 585) +* BFD_RELOC_386_TLS_IE: howto manager. (line 584) +* BFD_RELOC_386_TLS_IE_32: howto manager. (line 590) +* BFD_RELOC_386_TLS_LDM: howto manager. (line 588) +* BFD_RELOC_386_TLS_LDO_32: howto manager. (line 589) +* BFD_RELOC_386_TLS_LE: howto manager. (line 586) +* BFD_RELOC_386_TLS_LE_32: howto manager. (line 591) +* BFD_RELOC_386_TLS_TPOFF: howto manager. (line 583) +* BFD_RELOC_386_TLS_TPOFF32: howto manager. (line 594) +* BFD_RELOC_390_12: howto manager. (line 1992) +* BFD_RELOC_390_20: howto manager. (line 2104) +* BFD_RELOC_390_COPY: howto manager. (line 2001) +* BFD_RELOC_390_GLOB_DAT: howto manager. (line 2004) +* BFD_RELOC_390_GOT12: howto manager. (line 1995) +* BFD_RELOC_390_GOT16: howto manager. (line 2016) +* BFD_RELOC_390_GOT20: howto manager. (line 2105) +* BFD_RELOC_390_GOT64: howto manager. (line 2046) +* BFD_RELOC_390_GOTENT: howto manager. (line 2052) +* BFD_RELOC_390_GOTOFF64: howto manager. (line 2055) +* BFD_RELOC_390_GOTPC: howto manager. (line 2013) +* BFD_RELOC_390_GOTPCDBL: howto manager. (line 2043) +* BFD_RELOC_390_GOTPLT12: howto manager. (line 2058) +* BFD_RELOC_390_GOTPLT16: howto manager. (line 2061) +* BFD_RELOC_390_GOTPLT20: howto manager. (line 2106) +* BFD_RELOC_390_GOTPLT32: howto manager. (line 2064) +* BFD_RELOC_390_GOTPLT64: howto manager. (line 2067) +* BFD_RELOC_390_GOTPLTENT: howto manager. (line 2070) +* BFD_RELOC_390_IRELATIVE: howto manager. (line 2110) +* BFD_RELOC_390_JMP_SLOT: howto manager. (line 2007) +* BFD_RELOC_390_PC12DBL: howto manager. (line 2019) +* BFD_RELOC_390_PC16DBL: howto manager. (line 2025) +* BFD_RELOC_390_PC24DBL: howto manager. (line 2031) +* BFD_RELOC_390_PC32DBL: howto manager. (line 2037) +* BFD_RELOC_390_PLT12DBL: howto manager. (line 2022) +* BFD_RELOC_390_PLT16DBL: howto manager. (line 2028) +* BFD_RELOC_390_PLT24DBL: howto manager. (line 2034) +* BFD_RELOC_390_PLT32: howto manager. (line 1998) +* BFD_RELOC_390_PLT32DBL: howto manager. (line 2040) +* BFD_RELOC_390_PLT64: howto manager. (line 2049) +* BFD_RELOC_390_PLTOFF16: howto manager. (line 2073) +* BFD_RELOC_390_PLTOFF32: howto manager. (line 2076) +* BFD_RELOC_390_PLTOFF64: howto manager. (line 2079) +* BFD_RELOC_390_RELATIVE: howto manager. (line 2010) +* BFD_RELOC_390_TLS_DTPMOD: howto manager. (line 2099) +* BFD_RELOC_390_TLS_DTPOFF: howto manager. (line 2100) +* BFD_RELOC_390_TLS_GD32: howto manager. (line 2085) +* BFD_RELOC_390_TLS_GD64: howto manager. (line 2086) +* BFD_RELOC_390_TLS_GDCALL: howto manager. (line 2083) +* BFD_RELOC_390_TLS_GOTIE12: howto manager. (line 2087) +* BFD_RELOC_390_TLS_GOTIE20: howto manager. (line 2107) +* BFD_RELOC_390_TLS_GOTIE32: howto manager. (line 2088) +* BFD_RELOC_390_TLS_GOTIE64: howto manager. (line 2089) +* BFD_RELOC_390_TLS_IE32: howto manager. (line 2092) +* BFD_RELOC_390_TLS_IE64: howto manager. (line 2093) +* BFD_RELOC_390_TLS_IEENT: howto manager. (line 2094) +* BFD_RELOC_390_TLS_LDCALL: howto manager. (line 2084) +* BFD_RELOC_390_TLS_LDM32: howto manager. (line 2090) +* BFD_RELOC_390_TLS_LDM64: howto manager. (line 2091) +* BFD_RELOC_390_TLS_LDO32: howto manager. (line 2097) +* BFD_RELOC_390_TLS_LDO64: howto manager. (line 2098) +* BFD_RELOC_390_TLS_LE32: howto manager. (line 2095) +* BFD_RELOC_390_TLS_LE64: howto manager. (line 2096) +* BFD_RELOC_390_TLS_LOAD: howto manager. (line 2082) +* BFD_RELOC_390_TLS_TPOFF: howto manager. (line 2101) * BFD_RELOC_64: howto manager. (line 26) * BFD_RELOC_64_PCREL: howto manager. (line 35) * BFD_RELOC_64_PLT_PCREL: howto manager. (line 60) @@ -11271,38 +11629,38 @@ BFD Index * BFD_RELOC_68K_TLS_LE32: howto manager. (line 93) * BFD_RELOC_68K_TLS_LE8: howto manager. (line 95) * BFD_RELOC_8: howto manager. (line 32) -* BFD_RELOC_860_COPY: howto manager. (line 2343) -* BFD_RELOC_860_GLOB_DAT: howto manager. (line 2344) -* BFD_RELOC_860_HAGOT: howto manager. (line 2369) -* BFD_RELOC_860_HAGOTOFF: howto manager. (line 2370) -* BFD_RELOC_860_HAPC: howto manager. (line 2371) -* BFD_RELOC_860_HIGH: howto manager. (line 2372) -* BFD_RELOC_860_HIGHADJ: howto manager. (line 2368) -* BFD_RELOC_860_HIGOT: howto manager. (line 2373) -* BFD_RELOC_860_HIGOTOFF: howto manager. (line 2374) -* BFD_RELOC_860_JUMP_SLOT: howto manager. (line 2345) -* BFD_RELOC_860_LOGOT0: howto manager. (line 2357) -* BFD_RELOC_860_LOGOT1: howto manager. (line 2359) -* BFD_RELOC_860_LOGOTOFF0: howto manager. (line 2361) -* BFD_RELOC_860_LOGOTOFF1: howto manager. (line 2363) -* BFD_RELOC_860_LOGOTOFF2: howto manager. (line 2365) -* BFD_RELOC_860_LOGOTOFF3: howto manager. (line 2366) -* BFD_RELOC_860_LOPC: howto manager. (line 2367) -* BFD_RELOC_860_LOW0: howto manager. (line 2350) -* BFD_RELOC_860_LOW1: howto manager. (line 2352) -* BFD_RELOC_860_LOW2: howto manager. (line 2354) -* BFD_RELOC_860_LOW3: howto manager. (line 2356) -* BFD_RELOC_860_PC16: howto manager. (line 2349) -* BFD_RELOC_860_PC26: howto manager. (line 2347) -* BFD_RELOC_860_PLT26: howto manager. (line 2348) -* BFD_RELOC_860_RELATIVE: howto manager. (line 2346) -* BFD_RELOC_860_SPGOT0: howto manager. (line 2358) -* BFD_RELOC_860_SPGOT1: howto manager. (line 2360) -* BFD_RELOC_860_SPGOTOFF0: howto manager. (line 2362) -* BFD_RELOC_860_SPGOTOFF1: howto manager. (line 2364) -* BFD_RELOC_860_SPLIT0: howto manager. (line 2351) -* BFD_RELOC_860_SPLIT1: howto manager. (line 2353) -* BFD_RELOC_860_SPLIT2: howto manager. (line 2355) +* BFD_RELOC_860_COPY: howto manager. (line 2537) +* BFD_RELOC_860_GLOB_DAT: howto manager. (line 2538) +* BFD_RELOC_860_HAGOT: howto manager. (line 2563) +* BFD_RELOC_860_HAGOTOFF: howto manager. (line 2564) +* BFD_RELOC_860_HAPC: howto manager. (line 2565) +* BFD_RELOC_860_HIGH: howto manager. (line 2566) +* BFD_RELOC_860_HIGHADJ: howto manager. (line 2562) +* BFD_RELOC_860_HIGOT: howto manager. (line 2567) +* BFD_RELOC_860_HIGOTOFF: howto manager. (line 2568) +* BFD_RELOC_860_JUMP_SLOT: howto manager. (line 2539) +* BFD_RELOC_860_LOGOT0: howto manager. (line 2551) +* BFD_RELOC_860_LOGOT1: howto manager. (line 2553) +* BFD_RELOC_860_LOGOTOFF0: howto manager. (line 2555) +* BFD_RELOC_860_LOGOTOFF1: howto manager. (line 2557) +* BFD_RELOC_860_LOGOTOFF2: howto manager. (line 2559) +* BFD_RELOC_860_LOGOTOFF3: howto manager. (line 2560) +* BFD_RELOC_860_LOPC: howto manager. (line 2561) +* BFD_RELOC_860_LOW0: howto manager. (line 2544) +* BFD_RELOC_860_LOW1: howto manager. (line 2546) +* BFD_RELOC_860_LOW2: howto manager. (line 2548) +* BFD_RELOC_860_LOW3: howto manager. (line 2550) +* BFD_RELOC_860_PC16: howto manager. (line 2543) +* BFD_RELOC_860_PC26: howto manager. (line 2541) +* BFD_RELOC_860_PLT26: howto manager. (line 2542) +* BFD_RELOC_860_RELATIVE: howto manager. (line 2540) +* BFD_RELOC_860_SPGOT0: howto manager. (line 2552) +* BFD_RELOC_860_SPGOT1: howto manager. (line 2554) +* BFD_RELOC_860_SPGOTOFF0: howto manager. (line 2556) +* BFD_RELOC_860_SPGOTOFF1: howto manager. (line 2558) +* BFD_RELOC_860_SPLIT0: howto manager. (line 2545) +* BFD_RELOC_860_SPLIT1: howto manager. (line 2547) +* BFD_RELOC_860_SPLIT2: howto manager. (line 2549) * BFD_RELOC_8_BASEREL: howto manager. (line 103) * BFD_RELOC_8_FFnn: howto manager. (line 107) * BFD_RELOC_8_GOT_PCREL: howto manager. (line 53) @@ -11310,67 +11668,89 @@ BFD Index * BFD_RELOC_8_PCREL: howto manager. (line 40) * BFD_RELOC_8_PLT_PCREL: howto manager. (line 64) * BFD_RELOC_8_PLTOFF: howto manager. (line 71) -* BFD_RELOC_AARCH64_ADD_LO12: howto manager. (line 2708) -* BFD_RELOC_AARCH64_ADR_GOT_PAGE: howto manager. (line 2720) -* BFD_RELOC_AARCH64_ADR_HI21_NC_PCREL: howto manager. (line 2729) -* BFD_RELOC_AARCH64_ADR_HI21_PCREL: howto manager. (line 2725) -* BFD_RELOC_AARCH64_ADR_LO21_PCREL: howto manager. (line 2734) -* BFD_RELOC_AARCH64_BRANCH19: howto manager. (line 2738) -* BFD_RELOC_AARCH64_CALL26: howto manager. (line 2743) -* BFD_RELOC_AARCH64_GAS_INTERNAL_FIXUP: howto manager. (line 2748) -* BFD_RELOC_AARCH64_GOT_LD_PREL19: howto manager. (line 2713) -* BFD_RELOC_AARCH64_JUMP26: howto manager. (line 2752) -* BFD_RELOC_AARCH64_LD64_GOT_LO12_NC: howto manager. (line 2762) -* BFD_RELOC_AARCH64_LD_LO19_PCREL: howto manager. (line 2757) -* BFD_RELOC_AARCH64_LDST128_LO12: howto manager. (line 2792) -* BFD_RELOC_AARCH64_LDST16_LO12: howto manager. (line 2777) -* BFD_RELOC_AARCH64_LDST32_LO12: howto manager. (line 2782) -* BFD_RELOC_AARCH64_LDST64_LO12: howto manager. (line 2787) -* BFD_RELOC_AARCH64_LDST8_LO12: howto manager. (line 2772) -* BFD_RELOC_AARCH64_LDST_LO12: howto manager. (line 2767) -* BFD_RELOC_AARCH64_MOVW_G0: howto manager. (line 2797) -* BFD_RELOC_AARCH64_MOVW_G0_NC: howto manager. (line 2806) -* BFD_RELOC_AARCH64_MOVW_G0_S: howto manager. (line 2801) -* BFD_RELOC_AARCH64_MOVW_G1: howto manager. (line 2810) -* BFD_RELOC_AARCH64_MOVW_G1_NC: howto manager. (line 2814) -* BFD_RELOC_AARCH64_MOVW_G1_S: howto manager. (line 2818) -* BFD_RELOC_AARCH64_MOVW_G2: howto manager. (line 2823) -* BFD_RELOC_AARCH64_MOVW_G2_NC: howto manager. (line 2827) -* BFD_RELOC_AARCH64_MOVW_G2_S: howto manager. (line 2831) -* BFD_RELOC_AARCH64_MOVW_G3: howto manager. (line 2836) -* BFD_RELOC_AARCH64_TLS_DTPMOD64: howto manager. (line 2923) -* BFD_RELOC_AARCH64_TLS_DTPREL64: howto manager. (line 2926) -* BFD_RELOC_AARCH64_TLS_TPREL64: howto manager. (line 2929) -* BFD_RELOC_AARCH64_TLSDESC: howto manager. (line 2840) -* BFD_RELOC_AARCH64_TLSDESC_ADD: howto manager. (line 2843) -* BFD_RELOC_AARCH64_TLSDESC_ADD_LO12_NC: howto manager. (line 2846) -* BFD_RELOC_AARCH64_TLSDESC_ADR_PAGE: howto manager. (line 2849) -* BFD_RELOC_AARCH64_TLSDESC_ADR_PREL21: howto manager. (line 2852) -* BFD_RELOC_AARCH64_TLSDESC_CALL: howto manager. (line 2855) -* BFD_RELOC_AARCH64_TLSDESC_LD64_LO12_NC: howto manager. (line 2858) -* BFD_RELOC_AARCH64_TLSDESC_LD64_PREL19: howto manager. (line 2861) -* BFD_RELOC_AARCH64_TLSDESC_LDR: howto manager. (line 2864) -* BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC: howto manager. (line 2867) -* BFD_RELOC_AARCH64_TLSDESC_OFF_G1: howto manager. (line 2870) -* BFD_RELOC_AARCH64_TLSGD_ADD_LO12_NC: howto manager. (line 2873) -* BFD_RELOC_AARCH64_TLSGD_ADR_PAGE21: howto manager. (line 2878) +* BFD_RELOC_AARCH64_16: howto manager. (line 2928) +* BFD_RELOC_AARCH64_16_PCREL: howto manager. (line 2935) +* BFD_RELOC_AARCH64_32: howto manager. (line 2927) +* BFD_RELOC_AARCH64_32_PCREL: howto manager. (line 2934) +* BFD_RELOC_AARCH64_64: howto manager. (line 2926) +* BFD_RELOC_AARCH64_64_PCREL: howto manager. (line 2933) +* BFD_RELOC_AARCH64_ADD_LO12: howto manager. (line 3000) +* BFD_RELOC_AARCH64_ADR_GOT_PAGE: howto manager. (line 3057) +* BFD_RELOC_AARCH64_ADR_HI21_NC_PCREL: howto manager. (line 2995) +* BFD_RELOC_AARCH64_ADR_HI21_PCREL: howto manager. (line 2991) +* BFD_RELOC_AARCH64_ADR_LO21_PCREL: howto manager. (line 2987) +* BFD_RELOC_AARCH64_BRANCH19: howto manager. (line 3015) +* BFD_RELOC_AARCH64_CALL26: howto manager. (line 3025) +* BFD_RELOC_AARCH64_COPY: howto manager. (line 3158) +* BFD_RELOC_AARCH64_GAS_INTERNAL_FIXUP: howto manager. (line 3192) +* BFD_RELOC_AARCH64_GLOB_DAT: howto manager. (line 3161) +* BFD_RELOC_AARCH64_GOT_LD_PREL19: howto manager. (line 3050) +* BFD_RELOC_AARCH64_IRELATIVE: howto manager. (line 3182) +* BFD_RELOC_AARCH64_JUMP26: howto manager. (line 3020) +* BFD_RELOC_AARCH64_JUMP_SLOT: howto manager. (line 3164) +* BFD_RELOC_AARCH64_LD32_GOT_LO12_NC: howto manager. (line 3067) +* BFD_RELOC_AARCH64_LD64_GOT_LO12_NC: howto manager. (line 3062) +* BFD_RELOC_AARCH64_LD_GOT_LO12_NC: howto manager. (line 3201) +* BFD_RELOC_AARCH64_LD_LO19_PCREL: howto manager. (line 2982) +* BFD_RELOC_AARCH64_LDST128_LO12: howto manager. (line 3045) +* BFD_RELOC_AARCH64_LDST16_LO12: howto manager. (line 3030) +* BFD_RELOC_AARCH64_LDST32_LO12: howto manager. (line 3035) +* BFD_RELOC_AARCH64_LDST64_LO12: howto manager. (line 3040) +* BFD_RELOC_AARCH64_LDST8_LO12: howto manager. (line 3005) +* BFD_RELOC_AARCH64_LDST_LO12: howto manager. (line 3196) +* BFD_RELOC_AARCH64_MOVW_G0: howto manager. (line 2939) +* BFD_RELOC_AARCH64_MOVW_G0_NC: howto manager. (line 2943) +* BFD_RELOC_AARCH64_MOVW_G0_S: howto manager. (line 2967) +* BFD_RELOC_AARCH64_MOVW_G1: howto manager. (line 2947) +* BFD_RELOC_AARCH64_MOVW_G1_NC: howto manager. (line 2951) +* BFD_RELOC_AARCH64_MOVW_G1_S: howto manager. (line 2972) +* BFD_RELOC_AARCH64_MOVW_G2: howto manager. (line 2955) +* BFD_RELOC_AARCH64_MOVW_G2_NC: howto manager. (line 2959) +* BFD_RELOC_AARCH64_MOVW_G2_S: howto manager. (line 2977) +* BFD_RELOC_AARCH64_MOVW_G3: howto manager. (line 2963) +* BFD_RELOC_AARCH64_NONE: howto manager. (line 2923) +* BFD_RELOC_AARCH64_RELATIVE: howto manager. (line 3167) +* BFD_RELOC_AARCH64_RELOC_END: howto manager. (line 3185) +* BFD_RELOC_AARCH64_RELOC_START: howto manager. (line 2917) +* BFD_RELOC_AARCH64_TLS_DTPMOD: howto manager. (line 3170) +* BFD_RELOC_AARCH64_TLS_DTPREL: howto manager. (line 3173) +* BFD_RELOC_AARCH64_TLS_TPREL: howto manager. (line 3176) +* BFD_RELOC_AARCH64_TLSDESC: howto manager. (line 3179) +* BFD_RELOC_AARCH64_TLSDESC_ADD: howto manager. (line 3152) +* BFD_RELOC_AARCH64_TLSDESC_ADD_LO12_NC: howto manager. (line 3140) +* BFD_RELOC_AARCH64_TLSDESC_ADR_PAGE21: howto manager. (line 3131) +* BFD_RELOC_AARCH64_TLSDESC_ADR_PREL21: howto manager. (line 3128) +* BFD_RELOC_AARCH64_TLSDESC_CALL: howto manager. (line 3155) +* BFD_RELOC_AARCH64_TLSDESC_LD32_LO12_NC: howto manager. (line 3137) +* BFD_RELOC_AARCH64_TLSDESC_LD64_LO12_NC: howto manager. (line 3134) +* BFD_RELOC_AARCH64_TLSDESC_LD_LO12_NC: howto manager. (line 3209) +* BFD_RELOC_AARCH64_TLSDESC_LD_PREL19: howto manager. (line 3125) +* BFD_RELOC_AARCH64_TLSDESC_LDR: howto manager. (line 3149) +* BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC: howto manager. (line 3146) +* BFD_RELOC_AARCH64_TLSDESC_OFF_G1: howto manager. (line 3143) +* BFD_RELOC_AARCH64_TLSGD_ADD_LO12_NC: howto manager. (line 3078) +* BFD_RELOC_AARCH64_TLSGD_ADR_PAGE21: howto manager. (line 3072) * BFD_RELOC_AARCH64_TLSIE_ADR_GOTTPREL_PAGE21: howto manager. - (line 2884) + (line 3089) +* BFD_RELOC_AARCH64_TLSIE_LD32_GOTTPREL_LO12_NC: howto manager. + (line 3095) * BFD_RELOC_AARCH64_TLSIE_LD64_GOTTPREL_LO12_NC: howto manager. - (line 2890) -* BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_PREL19: howto manager. (line 2887) + (line 3092) +* BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_LO12_NC: howto manager. + (line 3205) +* BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_PREL19: howto manager. (line 3098) * BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G0_NC: howto manager. - (line 2893) -* BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G1: howto manager. (line 2896) -* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_HI12: howto manager. (line 2899) -* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12: howto manager. (line 2902) -* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12_NC: howto manager. (line 2905) -* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0: howto manager. (line 2908) -* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0_NC: howto manager. (line 2911) -* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1: howto manager. (line 2914) -* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1_NC: howto manager. (line 2917) -* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G2: howto manager. (line 2920) -* BFD_RELOC_AARCH64_TSTBR14: howto manager. (line 2932) + (line 3086) +* BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G1: howto manager. (line 3083) +* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_HI12: howto manager. (line 3116) +* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12: howto manager. (line 3119) +* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12_NC: howto manager. (line 3122) +* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0: howto manager. (line 3110) +* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0_NC: howto manager. (line 3113) +* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1: howto manager. (line 3104) +* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1_NC: howto manager. (line 3107) +* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G2: howto manager. (line 3101) +* BFD_RELOC_AARCH64_TSTBR14: howto manager. (line 3010) * BFD_RELOC_ALPHA_BOH: howto manager. (line 323) * BFD_RELOC_ALPHA_BRSGP: howto manager. (line 306) * BFD_RELOC_ALPHA_BSR: howto manager. (line 315) @@ -11400,356 +11780,356 @@ BFD Index * BFD_RELOC_ALPHA_TPREL64: howto manager. (line 336) * BFD_RELOC_ALPHA_TPREL_HI16: howto manager. (line 337) * BFD_RELOC_ALPHA_TPREL_LO16: howto manager. (line 338) -* BFD_RELOC_ARC_B22_PCREL: howto manager. (line 1040) -* BFD_RELOC_ARC_B26: howto manager. (line 1045) -* BFD_RELOC_ARM_ADR_IMM: howto manager. (line 926) -* BFD_RELOC_ARM_ADRL_IMMEDIATE: howto manager. (line 912) -* BFD_RELOC_ARM_ALU_PC_G0: howto manager. (line 876) -* BFD_RELOC_ARM_ALU_PC_G0_NC: howto manager. (line 875) -* BFD_RELOC_ARM_ALU_PC_G1: howto manager. (line 878) -* BFD_RELOC_ARM_ALU_PC_G1_NC: howto manager. (line 877) -* BFD_RELOC_ARM_ALU_PC_G2: howto manager. (line 879) -* BFD_RELOC_ARM_ALU_SB_G0: howto manager. (line 890) -* BFD_RELOC_ARM_ALU_SB_G0_NC: howto manager. (line 889) -* BFD_RELOC_ARM_ALU_SB_G1: howto manager. (line 892) -* BFD_RELOC_ARM_ALU_SB_G1_NC: howto manager. (line 891) -* BFD_RELOC_ARM_ALU_SB_G2: howto manager. (line 893) -* BFD_RELOC_ARM_CP_OFF_IMM: howto manager. (line 922) -* BFD_RELOC_ARM_CP_OFF_IMM_S2: howto manager. (line 923) -* BFD_RELOC_ARM_GLOB_DAT: howto manager. (line 850) -* BFD_RELOC_ARM_GOT32: howto manager. (line 851) -* BFD_RELOC_ARM_GOT_PREL: howto manager. (line 856) -* BFD_RELOC_ARM_GOTOFF: howto manager. (line 854) -* BFD_RELOC_ARM_GOTPC: howto manager. (line 855) -* BFD_RELOC_ARM_HVC: howto manager. (line 919) -* BFD_RELOC_ARM_HWLITERAL: howto manager. (line 933) -* BFD_RELOC_ARM_IMMEDIATE: howto manager. (line 911) -* BFD_RELOC_ARM_IN_POOL: howto manager. (line 929) -* BFD_RELOC_ARM_IRELATIVE: howto manager. (line 908) -* BFD_RELOC_ARM_JUMP_SLOT: howto manager. (line 849) -* BFD_RELOC_ARM_LDC_PC_G0: howto manager. (line 886) -* BFD_RELOC_ARM_LDC_PC_G1: howto manager. (line 887) -* BFD_RELOC_ARM_LDC_PC_G2: howto manager. (line 888) -* BFD_RELOC_ARM_LDC_SB_G0: howto manager. (line 900) -* BFD_RELOC_ARM_LDC_SB_G1: howto manager. (line 901) -* BFD_RELOC_ARM_LDC_SB_G2: howto manager. (line 902) -* BFD_RELOC_ARM_LDR_IMM: howto manager. (line 927) -* BFD_RELOC_ARM_LDR_PC_G0: howto manager. (line 880) -* BFD_RELOC_ARM_LDR_PC_G1: howto manager. (line 881) -* BFD_RELOC_ARM_LDR_PC_G2: howto manager. (line 882) -* BFD_RELOC_ARM_LDR_SB_G0: howto manager. (line 894) -* BFD_RELOC_ARM_LDR_SB_G1: howto manager. (line 895) -* BFD_RELOC_ARM_LDR_SB_G2: howto manager. (line 896) -* BFD_RELOC_ARM_LDRS_PC_G0: howto manager. (line 883) -* BFD_RELOC_ARM_LDRS_PC_G1: howto manager. (line 884) -* BFD_RELOC_ARM_LDRS_PC_G2: howto manager. (line 885) -* BFD_RELOC_ARM_LDRS_SB_G0: howto manager. (line 897) -* BFD_RELOC_ARM_LDRS_SB_G1: howto manager. (line 898) -* BFD_RELOC_ARM_LDRS_SB_G2: howto manager. (line 899) -* BFD_RELOC_ARM_LITERAL: howto manager. (line 928) -* BFD_RELOC_ARM_MOVT: howto manager. (line 840) -* BFD_RELOC_ARM_MOVT_PCREL: howto manager. (line 842) -* BFD_RELOC_ARM_MOVW: howto manager. (line 839) -* BFD_RELOC_ARM_MOVW_PCREL: howto manager. (line 841) -* BFD_RELOC_ARM_MULTI: howto manager. (line 921) -* BFD_RELOC_ARM_OFFSET_IMM: howto manager. (line 813) -* BFD_RELOC_ARM_OFFSET_IMM8: howto manager. (line 930) -* BFD_RELOC_ARM_PCREL_BLX: howto manager. (line 784) -* BFD_RELOC_ARM_PCREL_BRANCH: howto manager. (line 780) -* BFD_RELOC_ARM_PCREL_CALL: howto manager. (line 794) -* BFD_RELOC_ARM_PCREL_JUMP: howto manager. (line 798) -* BFD_RELOC_ARM_PLT32: howto manager. (line 852) -* BFD_RELOC_ARM_PREL31: howto manager. (line 836) -* BFD_RELOC_ARM_RELATIVE: howto manager. (line 853) -* BFD_RELOC_ARM_ROSEGREL32: howto manager. (line 825) -* BFD_RELOC_ARM_SBREL32: howto manager. (line 828) -* BFD_RELOC_ARM_SHIFT_IMM: howto manager. (line 917) -* BFD_RELOC_ARM_SMC: howto manager. (line 918) -* BFD_RELOC_ARM_SWI: howto manager. (line 920) -* BFD_RELOC_ARM_T32_ADD_IMM: howto manager. (line 914) -* BFD_RELOC_ARM_T32_ADD_PC12: howto manager. (line 916) -* BFD_RELOC_ARM_T32_CP_OFF_IMM: howto manager. (line 924) -* BFD_RELOC_ARM_T32_CP_OFF_IMM_S2: howto manager. (line 925) -* BFD_RELOC_ARM_T32_IMM12: howto manager. (line 915) -* BFD_RELOC_ARM_T32_IMMEDIATE: howto manager. (line 913) -* BFD_RELOC_ARM_T32_OFFSET_IMM: howto manager. (line 932) -* BFD_RELOC_ARM_T32_OFFSET_U8: howto manager. (line 931) -* BFD_RELOC_ARM_TARGET1: howto manager. (line 821) -* BFD_RELOC_ARM_TARGET2: howto manager. (line 831) -* BFD_RELOC_ARM_THM_TLS_CALL: howto manager. (line 869) -* BFD_RELOC_ARM_THM_TLS_DESCSEQ: howto manager. (line 871) -* BFD_RELOC_ARM_THUMB_ADD: howto manager. (line 934) -* BFD_RELOC_ARM_THUMB_IMM: howto manager. (line 935) -* BFD_RELOC_ARM_THUMB_MOVT: howto manager. (line 844) -* BFD_RELOC_ARM_THUMB_MOVT_PCREL: howto manager. (line 846) -* BFD_RELOC_ARM_THUMB_MOVW: howto manager. (line 843) -* BFD_RELOC_ARM_THUMB_MOVW_PCREL: howto manager. (line 845) -* BFD_RELOC_ARM_THUMB_OFFSET: howto manager. (line 817) -* BFD_RELOC_ARM_THUMB_SHIFT: howto manager. (line 936) -* BFD_RELOC_ARM_TLS_CALL: howto manager. (line 868) -* BFD_RELOC_ARM_TLS_DESC: howto manager. (line 872) -* BFD_RELOC_ARM_TLS_DESCSEQ: howto manager. (line 870) -* BFD_RELOC_ARM_TLS_DTPMOD32: howto manager. (line 863) -* BFD_RELOC_ARM_TLS_DTPOFF32: howto manager. (line 862) -* BFD_RELOC_ARM_TLS_GD32: howto manager. (line 859) -* BFD_RELOC_ARM_TLS_GOTDESC: howto manager. (line 867) -* BFD_RELOC_ARM_TLS_IE32: howto manager. (line 865) -* BFD_RELOC_ARM_TLS_LDM32: howto manager. (line 861) -* BFD_RELOC_ARM_TLS_LDO32: howto manager. (line 860) -* BFD_RELOC_ARM_TLS_LE32: howto manager. (line 866) -* BFD_RELOC_ARM_TLS_TPOFF32: howto manager. (line 864) -* BFD_RELOC_ARM_V4BX: howto manager. (line 905) -* BFD_RELOC_AVR_13_PCREL: howto manager. (line 1635) -* BFD_RELOC_AVR_16_PM: howto manager. (line 1639) -* BFD_RELOC_AVR_6: howto manager. (line 1726) -* BFD_RELOC_AVR_6_ADIW: howto manager. (line 1730) -* BFD_RELOC_AVR_7_PCREL: howto manager. (line 1631) -* BFD_RELOC_AVR_8_HI: howto manager. (line 1738) -* BFD_RELOC_AVR_8_HLO: howto manager. (line 1742) -* BFD_RELOC_AVR_8_LO: howto manager. (line 1734) -* BFD_RELOC_AVR_CALL: howto manager. (line 1718) -* BFD_RELOC_AVR_HH8_LDI: howto manager. (line 1651) -* BFD_RELOC_AVR_HH8_LDI_NEG: howto manager. (line 1670) -* BFD_RELOC_AVR_HH8_LDI_PM: howto manager. (line 1699) -* BFD_RELOC_AVR_HH8_LDI_PM_NEG: howto manager. (line 1713) -* BFD_RELOC_AVR_HI8_LDI: howto manager. (line 1647) -* BFD_RELOC_AVR_HI8_LDI_GS: howto manager. (line 1693) -* BFD_RELOC_AVR_HI8_LDI_NEG: howto manager. (line 1665) -* BFD_RELOC_AVR_HI8_LDI_PM: howto manager. (line 1689) -* BFD_RELOC_AVR_HI8_LDI_PM_NEG: howto manager. (line 1708) -* BFD_RELOC_AVR_LDI: howto manager. (line 1722) -* BFD_RELOC_AVR_LO8_LDI: howto manager. (line 1643) -* BFD_RELOC_AVR_LO8_LDI_GS: howto manager. (line 1683) -* BFD_RELOC_AVR_LO8_LDI_NEG: howto manager. (line 1660) -* BFD_RELOC_AVR_LO8_LDI_PM: howto manager. (line 1679) -* BFD_RELOC_AVR_LO8_LDI_PM_NEG: howto manager. (line 1704) -* BFD_RELOC_AVR_MS8_LDI: howto manager. (line 1656) -* BFD_RELOC_AVR_MS8_LDI_NEG: howto manager. (line 1675) -* BFD_RELOC_BFIN_10_PCREL: howto manager. (line 1065) -* BFD_RELOC_BFIN_11_PCREL: howto manager. (line 1068) -* BFD_RELOC_BFIN_12_PCREL_JUMP: howto manager. (line 1071) -* BFD_RELOC_BFIN_12_PCREL_JUMP_S: howto manager. (line 1074) -* BFD_RELOC_BFIN_16_HIGH: howto manager. (line 1053) -* BFD_RELOC_BFIN_16_IMM: howto manager. (line 1050) -* BFD_RELOC_BFIN_16_LOW: howto manager. (line 1062) -* BFD_RELOC_BFIN_24_PCREL_CALL_X: howto manager. (line 1077) -* BFD_RELOC_BFIN_24_PCREL_JUMP_L: howto manager. (line 1080) -* BFD_RELOC_BFIN_4_PCREL: howto manager. (line 1056) -* BFD_RELOC_BFIN_5_PCREL: howto manager. (line 1059) -* BFD_RELOC_BFIN_FUNCDESC: howto manager. (line 1086) -* BFD_RELOC_BFIN_FUNCDESC_GOT17M4: howto manager. (line 1087) -* BFD_RELOC_BFIN_FUNCDESC_GOTHI: howto manager. (line 1088) -* BFD_RELOC_BFIN_FUNCDESC_GOTLO: howto manager. (line 1089) -* BFD_RELOC_BFIN_FUNCDESC_GOTOFF17M4: howto manager. (line 1091) -* BFD_RELOC_BFIN_FUNCDESC_GOTOFFHI: howto manager. (line 1092) -* BFD_RELOC_BFIN_FUNCDESC_GOTOFFLO: howto manager. (line 1093) -* BFD_RELOC_BFIN_FUNCDESC_VALUE: howto manager. (line 1090) -* BFD_RELOC_BFIN_GOT: howto manager. (line 1099) -* BFD_RELOC_BFIN_GOT17M4: howto manager. (line 1083) -* BFD_RELOC_BFIN_GOTHI: howto manager. (line 1084) -* BFD_RELOC_BFIN_GOTLO: howto manager. (line 1085) -* BFD_RELOC_BFIN_GOTOFF17M4: howto manager. (line 1094) -* BFD_RELOC_BFIN_GOTOFFHI: howto manager. (line 1095) -* BFD_RELOC_BFIN_GOTOFFLO: howto manager. (line 1096) -* BFD_RELOC_BFIN_PLTPC: howto manager. (line 1102) -* BFD_RELOC_C6000_ABS_H16: howto manager. (line 1454) -* BFD_RELOC_C6000_ABS_L16: howto manager. (line 1453) -* BFD_RELOC_C6000_ABS_S16: howto manager. (line 1452) -* BFD_RELOC_C6000_ALIGN: howto manager. (line 1475) -* BFD_RELOC_C6000_COPY: howto manager. (line 1470) -* BFD_RELOC_C6000_DSBT_INDEX: howto manager. (line 1468) -* BFD_RELOC_C6000_EHTYPE: howto manager. (line 1472) -* BFD_RELOC_C6000_FPHEAD: howto manager. (line 1476) -* BFD_RELOC_C6000_JUMP_SLOT: howto manager. (line 1471) -* BFD_RELOC_C6000_NOCMP: howto manager. (line 1477) -* BFD_RELOC_C6000_PCR_H16: howto manager. (line 1473) -* BFD_RELOC_C6000_PCR_L16: howto manager. (line 1474) -* BFD_RELOC_C6000_PCR_S10: howto manager. (line 1450) -* BFD_RELOC_C6000_PCR_S12: howto manager. (line 1449) -* BFD_RELOC_C6000_PCR_S21: howto manager. (line 1448) -* BFD_RELOC_C6000_PCR_S7: howto manager. (line 1451) -* BFD_RELOC_C6000_PREL31: howto manager. (line 1469) -* BFD_RELOC_C6000_SBR_GOT_H16_W: howto manager. (line 1467) -* BFD_RELOC_C6000_SBR_GOT_L16_W: howto manager. (line 1466) -* BFD_RELOC_C6000_SBR_GOT_U15_W: howto manager. (line 1465) -* BFD_RELOC_C6000_SBR_H16_B: howto manager. (line 1462) -* BFD_RELOC_C6000_SBR_H16_H: howto manager. (line 1463) -* BFD_RELOC_C6000_SBR_H16_W: howto manager. (line 1464) -* BFD_RELOC_C6000_SBR_L16_B: howto manager. (line 1459) -* BFD_RELOC_C6000_SBR_L16_H: howto manager. (line 1460) -* BFD_RELOC_C6000_SBR_L16_W: howto manager. (line 1461) -* BFD_RELOC_C6000_SBR_S16: howto manager. (line 1458) -* BFD_RELOC_C6000_SBR_U15_B: howto manager. (line 1455) -* BFD_RELOC_C6000_SBR_U15_H: howto manager. (line 1456) -* BFD_RELOC_C6000_SBR_U15_W: howto manager. (line 1457) +* BFD_RELOC_ARC_B22_PCREL: howto manager. (line 1049) +* BFD_RELOC_ARC_B26: howto manager. (line 1054) +* BFD_RELOC_ARM_ADR_IMM: howto manager. (line 935) +* BFD_RELOC_ARM_ADRL_IMMEDIATE: howto manager. (line 921) +* BFD_RELOC_ARM_ALU_PC_G0: howto manager. (line 885) +* BFD_RELOC_ARM_ALU_PC_G0_NC: howto manager. (line 884) +* BFD_RELOC_ARM_ALU_PC_G1: howto manager. (line 887) +* BFD_RELOC_ARM_ALU_PC_G1_NC: howto manager. (line 886) +* BFD_RELOC_ARM_ALU_PC_G2: howto manager. (line 888) +* BFD_RELOC_ARM_ALU_SB_G0: howto manager. (line 899) +* BFD_RELOC_ARM_ALU_SB_G0_NC: howto manager. (line 898) +* BFD_RELOC_ARM_ALU_SB_G1: howto manager. (line 901) +* BFD_RELOC_ARM_ALU_SB_G1_NC: howto manager. (line 900) +* BFD_RELOC_ARM_ALU_SB_G2: howto manager. (line 902) +* BFD_RELOC_ARM_CP_OFF_IMM: howto manager. (line 931) +* BFD_RELOC_ARM_CP_OFF_IMM_S2: howto manager. (line 932) +* BFD_RELOC_ARM_GLOB_DAT: howto manager. (line 859) +* BFD_RELOC_ARM_GOT32: howto manager. (line 860) +* BFD_RELOC_ARM_GOT_PREL: howto manager. (line 865) +* BFD_RELOC_ARM_GOTOFF: howto manager. (line 863) +* BFD_RELOC_ARM_GOTPC: howto manager. (line 864) +* BFD_RELOC_ARM_HVC: howto manager. (line 928) +* BFD_RELOC_ARM_HWLITERAL: howto manager. (line 942) +* BFD_RELOC_ARM_IMMEDIATE: howto manager. (line 920) +* BFD_RELOC_ARM_IN_POOL: howto manager. (line 938) +* BFD_RELOC_ARM_IRELATIVE: howto manager. (line 917) +* BFD_RELOC_ARM_JUMP_SLOT: howto manager. (line 858) +* BFD_RELOC_ARM_LDC_PC_G0: howto manager. (line 895) +* BFD_RELOC_ARM_LDC_PC_G1: howto manager. (line 896) +* BFD_RELOC_ARM_LDC_PC_G2: howto manager. (line 897) +* BFD_RELOC_ARM_LDC_SB_G0: howto manager. (line 909) +* BFD_RELOC_ARM_LDC_SB_G1: howto manager. (line 910) +* BFD_RELOC_ARM_LDC_SB_G2: howto manager. (line 911) +* BFD_RELOC_ARM_LDR_IMM: howto manager. (line 936) +* BFD_RELOC_ARM_LDR_PC_G0: howto manager. (line 889) +* BFD_RELOC_ARM_LDR_PC_G1: howto manager. (line 890) +* BFD_RELOC_ARM_LDR_PC_G2: howto manager. (line 891) +* BFD_RELOC_ARM_LDR_SB_G0: howto manager. (line 903) +* BFD_RELOC_ARM_LDR_SB_G1: howto manager. (line 904) +* BFD_RELOC_ARM_LDR_SB_G2: howto manager. (line 905) +* BFD_RELOC_ARM_LDRS_PC_G0: howto manager. (line 892) +* BFD_RELOC_ARM_LDRS_PC_G1: howto manager. (line 893) +* BFD_RELOC_ARM_LDRS_PC_G2: howto manager. (line 894) +* BFD_RELOC_ARM_LDRS_SB_G0: howto manager. (line 906) +* BFD_RELOC_ARM_LDRS_SB_G1: howto manager. (line 907) +* BFD_RELOC_ARM_LDRS_SB_G2: howto manager. (line 908) +* BFD_RELOC_ARM_LITERAL: howto manager. (line 937) +* BFD_RELOC_ARM_MOVT: howto manager. (line 849) +* BFD_RELOC_ARM_MOVT_PCREL: howto manager. (line 851) +* BFD_RELOC_ARM_MOVW: howto manager. (line 848) +* BFD_RELOC_ARM_MOVW_PCREL: howto manager. (line 850) +* BFD_RELOC_ARM_MULTI: howto manager. (line 930) +* BFD_RELOC_ARM_OFFSET_IMM: howto manager. (line 822) +* BFD_RELOC_ARM_OFFSET_IMM8: howto manager. (line 939) +* BFD_RELOC_ARM_PCREL_BLX: howto manager. (line 793) +* BFD_RELOC_ARM_PCREL_BRANCH: howto manager. (line 789) +* BFD_RELOC_ARM_PCREL_CALL: howto manager. (line 803) +* BFD_RELOC_ARM_PCREL_JUMP: howto manager. (line 807) +* BFD_RELOC_ARM_PLT32: howto manager. (line 861) +* BFD_RELOC_ARM_PREL31: howto manager. (line 845) +* BFD_RELOC_ARM_RELATIVE: howto manager. (line 862) +* BFD_RELOC_ARM_ROSEGREL32: howto manager. (line 834) +* BFD_RELOC_ARM_SBREL32: howto manager. (line 837) +* BFD_RELOC_ARM_SHIFT_IMM: howto manager. (line 926) +* BFD_RELOC_ARM_SMC: howto manager. (line 927) +* BFD_RELOC_ARM_SWI: howto manager. (line 929) +* BFD_RELOC_ARM_T32_ADD_IMM: howto manager. (line 923) +* BFD_RELOC_ARM_T32_ADD_PC12: howto manager. (line 925) +* BFD_RELOC_ARM_T32_CP_OFF_IMM: howto manager. (line 933) +* BFD_RELOC_ARM_T32_CP_OFF_IMM_S2: howto manager. (line 934) +* BFD_RELOC_ARM_T32_IMM12: howto manager. (line 924) +* BFD_RELOC_ARM_T32_IMMEDIATE: howto manager. (line 922) +* BFD_RELOC_ARM_T32_OFFSET_IMM: howto manager. (line 941) +* BFD_RELOC_ARM_T32_OFFSET_U8: howto manager. (line 940) +* BFD_RELOC_ARM_TARGET1: howto manager. (line 830) +* BFD_RELOC_ARM_TARGET2: howto manager. (line 840) +* BFD_RELOC_ARM_THM_TLS_CALL: howto manager. (line 878) +* BFD_RELOC_ARM_THM_TLS_DESCSEQ: howto manager. (line 880) +* BFD_RELOC_ARM_THUMB_ADD: howto manager. (line 943) +* BFD_RELOC_ARM_THUMB_IMM: howto manager. (line 944) +* BFD_RELOC_ARM_THUMB_MOVT: howto manager. (line 853) +* BFD_RELOC_ARM_THUMB_MOVT_PCREL: howto manager. (line 855) +* BFD_RELOC_ARM_THUMB_MOVW: howto manager. (line 852) +* BFD_RELOC_ARM_THUMB_MOVW_PCREL: howto manager. (line 854) +* BFD_RELOC_ARM_THUMB_OFFSET: howto manager. (line 826) +* BFD_RELOC_ARM_THUMB_SHIFT: howto manager. (line 945) +* BFD_RELOC_ARM_TLS_CALL: howto manager. (line 877) +* BFD_RELOC_ARM_TLS_DESC: howto manager. (line 881) +* BFD_RELOC_ARM_TLS_DESCSEQ: howto manager. (line 879) +* BFD_RELOC_ARM_TLS_DTPMOD32: howto manager. (line 872) +* BFD_RELOC_ARM_TLS_DTPOFF32: howto manager. (line 871) +* BFD_RELOC_ARM_TLS_GD32: howto manager. (line 868) +* BFD_RELOC_ARM_TLS_GOTDESC: howto manager. (line 876) +* BFD_RELOC_ARM_TLS_IE32: howto manager. (line 874) +* BFD_RELOC_ARM_TLS_LDM32: howto manager. (line 870) +* BFD_RELOC_ARM_TLS_LDO32: howto manager. (line 869) +* BFD_RELOC_ARM_TLS_LE32: howto manager. (line 875) +* BFD_RELOC_ARM_TLS_TPOFF32: howto manager. (line 873) +* BFD_RELOC_ARM_V4BX: howto manager. (line 914) +* BFD_RELOC_AVR_13_PCREL: howto manager. (line 1817) +* BFD_RELOC_AVR_16_PM: howto manager. (line 1821) +* BFD_RELOC_AVR_6: howto manager. (line 1908) +* BFD_RELOC_AVR_6_ADIW: howto manager. (line 1912) +* BFD_RELOC_AVR_7_PCREL: howto manager. (line 1813) +* BFD_RELOC_AVR_8_HI: howto manager. (line 1920) +* BFD_RELOC_AVR_8_HLO: howto manager. (line 1924) +* BFD_RELOC_AVR_8_LO: howto manager. (line 1916) +* BFD_RELOC_AVR_CALL: howto manager. (line 1900) +* BFD_RELOC_AVR_HH8_LDI: howto manager. (line 1833) +* BFD_RELOC_AVR_HH8_LDI_NEG: howto manager. (line 1852) +* BFD_RELOC_AVR_HH8_LDI_PM: howto manager. (line 1881) +* BFD_RELOC_AVR_HH8_LDI_PM_NEG: howto manager. (line 1895) +* BFD_RELOC_AVR_HI8_LDI: howto manager. (line 1829) +* BFD_RELOC_AVR_HI8_LDI_GS: howto manager. (line 1875) +* BFD_RELOC_AVR_HI8_LDI_NEG: howto manager. (line 1847) +* BFD_RELOC_AVR_HI8_LDI_PM: howto manager. (line 1871) +* BFD_RELOC_AVR_HI8_LDI_PM_NEG: howto manager. (line 1890) +* BFD_RELOC_AVR_LDI: howto manager. (line 1904) +* BFD_RELOC_AVR_LO8_LDI: howto manager. (line 1825) +* BFD_RELOC_AVR_LO8_LDI_GS: howto manager. (line 1865) +* BFD_RELOC_AVR_LO8_LDI_NEG: howto manager. (line 1842) +* BFD_RELOC_AVR_LO8_LDI_PM: howto manager. (line 1861) +* BFD_RELOC_AVR_LO8_LDI_PM_NEG: howto manager. (line 1886) +* BFD_RELOC_AVR_MS8_LDI: howto manager. (line 1838) +* BFD_RELOC_AVR_MS8_LDI_NEG: howto manager. (line 1857) +* BFD_RELOC_BFIN_10_PCREL: howto manager. (line 1074) +* BFD_RELOC_BFIN_11_PCREL: howto manager. (line 1077) +* BFD_RELOC_BFIN_12_PCREL_JUMP: howto manager. (line 1080) +* BFD_RELOC_BFIN_12_PCREL_JUMP_S: howto manager. (line 1083) +* BFD_RELOC_BFIN_16_HIGH: howto manager. (line 1062) +* BFD_RELOC_BFIN_16_IMM: howto manager. (line 1059) +* BFD_RELOC_BFIN_16_LOW: howto manager. (line 1071) +* BFD_RELOC_BFIN_24_PCREL_CALL_X: howto manager. (line 1086) +* BFD_RELOC_BFIN_24_PCREL_JUMP_L: howto manager. (line 1089) +* BFD_RELOC_BFIN_4_PCREL: howto manager. (line 1065) +* BFD_RELOC_BFIN_5_PCREL: howto manager. (line 1068) +* BFD_RELOC_BFIN_FUNCDESC: howto manager. (line 1095) +* BFD_RELOC_BFIN_FUNCDESC_GOT17M4: howto manager. (line 1096) +* BFD_RELOC_BFIN_FUNCDESC_GOTHI: howto manager. (line 1097) +* BFD_RELOC_BFIN_FUNCDESC_GOTLO: howto manager. (line 1098) +* BFD_RELOC_BFIN_FUNCDESC_GOTOFF17M4: howto manager. (line 1100) +* BFD_RELOC_BFIN_FUNCDESC_GOTOFFHI: howto manager. (line 1101) +* BFD_RELOC_BFIN_FUNCDESC_GOTOFFLO: howto manager. (line 1102) +* BFD_RELOC_BFIN_FUNCDESC_VALUE: howto manager. (line 1099) +* BFD_RELOC_BFIN_GOT: howto manager. (line 1108) +* BFD_RELOC_BFIN_GOT17M4: howto manager. (line 1092) +* BFD_RELOC_BFIN_GOTHI: howto manager. (line 1093) +* BFD_RELOC_BFIN_GOTLO: howto manager. (line 1094) +* BFD_RELOC_BFIN_GOTOFF17M4: howto manager. (line 1103) +* BFD_RELOC_BFIN_GOTOFFHI: howto manager. (line 1104) +* BFD_RELOC_BFIN_GOTOFFLO: howto manager. (line 1105) +* BFD_RELOC_BFIN_PLTPC: howto manager. (line 1111) +* BFD_RELOC_C6000_ABS_H16: howto manager. (line 1636) +* BFD_RELOC_C6000_ABS_L16: howto manager. (line 1635) +* BFD_RELOC_C6000_ABS_S16: howto manager. (line 1634) +* BFD_RELOC_C6000_ALIGN: howto manager. (line 1657) +* BFD_RELOC_C6000_COPY: howto manager. (line 1652) +* BFD_RELOC_C6000_DSBT_INDEX: howto manager. (line 1650) +* BFD_RELOC_C6000_EHTYPE: howto manager. (line 1654) +* BFD_RELOC_C6000_FPHEAD: howto manager. (line 1658) +* BFD_RELOC_C6000_JUMP_SLOT: howto manager. (line 1653) +* BFD_RELOC_C6000_NOCMP: howto manager. (line 1659) +* BFD_RELOC_C6000_PCR_H16: howto manager. (line 1655) +* BFD_RELOC_C6000_PCR_L16: howto manager. (line 1656) +* BFD_RELOC_C6000_PCR_S10: howto manager. (line 1632) +* BFD_RELOC_C6000_PCR_S12: howto manager. (line 1631) +* BFD_RELOC_C6000_PCR_S21: howto manager. (line 1630) +* BFD_RELOC_C6000_PCR_S7: howto manager. (line 1633) +* BFD_RELOC_C6000_PREL31: howto manager. (line 1651) +* BFD_RELOC_C6000_SBR_GOT_H16_W: howto manager. (line 1649) +* BFD_RELOC_C6000_SBR_GOT_L16_W: howto manager. (line 1648) +* BFD_RELOC_C6000_SBR_GOT_U15_W: howto manager. (line 1647) +* BFD_RELOC_C6000_SBR_H16_B: howto manager. (line 1644) +* BFD_RELOC_C6000_SBR_H16_H: howto manager. (line 1645) +* BFD_RELOC_C6000_SBR_H16_W: howto manager. (line 1646) +* BFD_RELOC_C6000_SBR_L16_B: howto manager. (line 1641) +* BFD_RELOC_C6000_SBR_L16_H: howto manager. (line 1642) +* BFD_RELOC_C6000_SBR_L16_W: howto manager. (line 1643) +* BFD_RELOC_C6000_SBR_S16: howto manager. (line 1640) +* BFD_RELOC_C6000_SBR_U15_B: howto manager. (line 1637) +* BFD_RELOC_C6000_SBR_U15_H: howto manager. (line 1638) +* BFD_RELOC_C6000_SBR_U15_W: howto manager. (line 1639) * bfd_reloc_code_type: howto manager. (line 10) -* BFD_RELOC_CR16_ABS20: howto manager. (line 2243) -* BFD_RELOC_CR16_ABS24: howto manager. (line 2244) -* BFD_RELOC_CR16_DISP16: howto manager. (line 2254) -* BFD_RELOC_CR16_DISP20: howto manager. (line 2255) -* BFD_RELOC_CR16_DISP24: howto manager. (line 2256) -* BFD_RELOC_CR16_DISP24a: howto manager. (line 2257) -* BFD_RELOC_CR16_DISP4: howto manager. (line 2252) -* BFD_RELOC_CR16_DISP8: howto manager. (line 2253) -* BFD_RELOC_CR16_GLOB_DAT: howto manager. (line 2263) -* BFD_RELOC_CR16_GOT_REGREL20: howto manager. (line 2261) -* BFD_RELOC_CR16_GOTC_REGREL20: howto manager. (line 2262) -* BFD_RELOC_CR16_IMM16: howto manager. (line 2247) -* BFD_RELOC_CR16_IMM20: howto manager. (line 2248) -* BFD_RELOC_CR16_IMM24: howto manager. (line 2249) -* BFD_RELOC_CR16_IMM32: howto manager. (line 2250) -* BFD_RELOC_CR16_IMM32a: howto manager. (line 2251) -* BFD_RELOC_CR16_IMM4: howto manager. (line 2245) -* BFD_RELOC_CR16_IMM8: howto manager. (line 2246) -* BFD_RELOC_CR16_NUM16: howto manager. (line 2232) -* BFD_RELOC_CR16_NUM32: howto manager. (line 2233) -* BFD_RELOC_CR16_NUM32a: howto manager. (line 2234) -* BFD_RELOC_CR16_NUM8: howto manager. (line 2231) -* BFD_RELOC_CR16_REGREL0: howto manager. (line 2235) -* BFD_RELOC_CR16_REGREL14: howto manager. (line 2238) -* BFD_RELOC_CR16_REGREL14a: howto manager. (line 2239) -* BFD_RELOC_CR16_REGREL16: howto manager. (line 2240) -* BFD_RELOC_CR16_REGREL20: howto manager. (line 2241) -* BFD_RELOC_CR16_REGREL20a: howto manager. (line 2242) -* BFD_RELOC_CR16_REGREL4: howto manager. (line 2236) -* BFD_RELOC_CR16_REGREL4a: howto manager. (line 2237) -* BFD_RELOC_CR16_SWITCH16: howto manager. (line 2259) -* BFD_RELOC_CR16_SWITCH32: howto manager. (line 2260) -* BFD_RELOC_CR16_SWITCH8: howto manager. (line 2258) -* BFD_RELOC_CRIS_16_DTPREL: howto manager. (line 2334) -* BFD_RELOC_CRIS_16_GOT: howto manager. (line 2310) -* BFD_RELOC_CRIS_16_GOT_GD: howto manager. (line 2330) -* BFD_RELOC_CRIS_16_GOT_TPREL: howto manager. (line 2336) -* BFD_RELOC_CRIS_16_GOTPLT: howto manager. (line 2316) -* BFD_RELOC_CRIS_16_TPREL: howto manager. (line 2338) -* BFD_RELOC_CRIS_32_DTPREL: howto manager. (line 2333) -* BFD_RELOC_CRIS_32_GD: howto manager. (line 2331) -* BFD_RELOC_CRIS_32_GOT: howto manager. (line 2307) -* BFD_RELOC_CRIS_32_GOT_GD: howto manager. (line 2329) -* BFD_RELOC_CRIS_32_GOT_TPREL: howto manager. (line 2335) -* BFD_RELOC_CRIS_32_GOTPLT: howto manager. (line 2313) -* BFD_RELOC_CRIS_32_GOTREL: howto manager. (line 2319) -* BFD_RELOC_CRIS_32_IE: howto manager. (line 2340) -* BFD_RELOC_CRIS_32_PLT_GOTREL: howto manager. (line 2322) -* BFD_RELOC_CRIS_32_PLT_PCREL: howto manager. (line 2325) -* BFD_RELOC_CRIS_32_TPREL: howto manager. (line 2337) -* BFD_RELOC_CRIS_BDISP8: howto manager. (line 2288) -* BFD_RELOC_CRIS_COPY: howto manager. (line 2301) -* BFD_RELOC_CRIS_DTP: howto manager. (line 2332) -* BFD_RELOC_CRIS_DTPMOD: howto manager. (line 2339) -* BFD_RELOC_CRIS_GLOB_DAT: howto manager. (line 2302) -* BFD_RELOC_CRIS_JUMP_SLOT: howto manager. (line 2303) -* BFD_RELOC_CRIS_LAPCQ_OFFSET: howto manager. (line 2296) -* BFD_RELOC_CRIS_RELATIVE: howto manager. (line 2304) -* BFD_RELOC_CRIS_SIGNED_16: howto manager. (line 2294) -* BFD_RELOC_CRIS_SIGNED_6: howto manager. (line 2290) -* BFD_RELOC_CRIS_SIGNED_8: howto manager. (line 2292) -* BFD_RELOC_CRIS_UNSIGNED_16: howto manager. (line 2295) -* BFD_RELOC_CRIS_UNSIGNED_4: howto manager. (line 2297) -* BFD_RELOC_CRIS_UNSIGNED_5: howto manager. (line 2289) -* BFD_RELOC_CRIS_UNSIGNED_6: howto manager. (line 2291) -* BFD_RELOC_CRIS_UNSIGNED_8: howto manager. (line 2293) -* BFD_RELOC_CRX_ABS16: howto manager. (line 2276) -* BFD_RELOC_CRX_ABS32: howto manager. (line 2277) -* BFD_RELOC_CRX_IMM16: howto manager. (line 2281) -* BFD_RELOC_CRX_IMM32: howto manager. (line 2282) -* BFD_RELOC_CRX_NUM16: howto manager. (line 2279) -* BFD_RELOC_CRX_NUM32: howto manager. (line 2280) -* BFD_RELOC_CRX_NUM8: howto manager. (line 2278) -* BFD_RELOC_CRX_REGREL12: howto manager. (line 2272) -* BFD_RELOC_CRX_REGREL22: howto manager. (line 2273) -* BFD_RELOC_CRX_REGREL28: howto manager. (line 2274) -* BFD_RELOC_CRX_REGREL32: howto manager. (line 2275) -* BFD_RELOC_CRX_REL16: howto manager. (line 2269) -* BFD_RELOC_CRX_REL24: howto manager. (line 2270) -* BFD_RELOC_CRX_REL32: howto manager. (line 2271) -* BFD_RELOC_CRX_REL4: howto manager. (line 2266) -* BFD_RELOC_CRX_REL8: howto manager. (line 2267) -* BFD_RELOC_CRX_REL8_CMP: howto manager. (line 2268) -* BFD_RELOC_CRX_SWITCH16: howto manager. (line 2284) -* BFD_RELOC_CRX_SWITCH32: howto manager. (line 2285) -* BFD_RELOC_CRX_SWITCH8: howto manager. (line 2283) -* BFD_RELOC_CTOR: howto manager. (line 774) -* BFD_RELOC_D10V_10_PCREL_L: howto manager. (line 1169) -* BFD_RELOC_D10V_10_PCREL_R: howto manager. (line 1165) -* BFD_RELOC_D10V_18: howto manager. (line 1174) -* BFD_RELOC_D10V_18_PCREL: howto manager. (line 1177) -* BFD_RELOC_D30V_15: howto manager. (line 1192) -* BFD_RELOC_D30V_15_PCREL: howto manager. (line 1196) -* BFD_RELOC_D30V_15_PCREL_R: howto manager. (line 1200) -* BFD_RELOC_D30V_21: howto manager. (line 1205) -* BFD_RELOC_D30V_21_PCREL: howto manager. (line 1209) -* BFD_RELOC_D30V_21_PCREL_R: howto manager. (line 1213) -* BFD_RELOC_D30V_32: howto manager. (line 1218) -* BFD_RELOC_D30V_32_PCREL: howto manager. (line 1221) -* BFD_RELOC_D30V_6: howto manager. (line 1180) -* BFD_RELOC_D30V_9_PCREL: howto manager. (line 1183) -* BFD_RELOC_D30V_9_PCREL_R: howto manager. (line 1187) -* BFD_RELOC_DLX_HI16_S: howto manager. (line 1224) -* BFD_RELOC_DLX_JMP26: howto manager. (line 1230) -* BFD_RELOC_DLX_LO16: howto manager. (line 1227) -* BFD_RELOC_EPIPHANY_HIGH: howto manager. (line 3135) -* BFD_RELOC_EPIPHANY_IMM11: howto manager. (line 3144) -* BFD_RELOC_EPIPHANY_IMM8: howto manager. (line 3148) -* BFD_RELOC_EPIPHANY_LOW: howto manager. (line 3138) -* BFD_RELOC_EPIPHANY_SIMM11: howto manager. (line 3141) -* BFD_RELOC_EPIPHANY_SIMM24: howto manager. (line 3132) -* BFD_RELOC_EPIPHANY_SIMM8: howto manager. (line 3129) -* BFD_RELOC_FR30_10_IN_8: howto manager. (line 1499) -* BFD_RELOC_FR30_12_PCREL: howto manager. (line 1507) -* BFD_RELOC_FR30_20: howto manager. (line 1483) -* BFD_RELOC_FR30_48: howto manager. (line 1480) -* BFD_RELOC_FR30_6_IN_4: howto manager. (line 1487) -* BFD_RELOC_FR30_8_IN_8: howto manager. (line 1491) -* BFD_RELOC_FR30_9_IN_8: howto manager. (line 1495) -* BFD_RELOC_FR30_9_PCREL: howto manager. (line 1503) -* BFD_RELOC_FRV_FUNCDESC: howto manager. (line 490) -* BFD_RELOC_FRV_FUNCDESC_GOT12: howto manager. (line 491) -* BFD_RELOC_FRV_FUNCDESC_GOTHI: howto manager. (line 492) -* BFD_RELOC_FRV_FUNCDESC_GOTLO: howto manager. (line 493) -* BFD_RELOC_FRV_FUNCDESC_GOTOFF12: howto manager. (line 495) -* BFD_RELOC_FRV_FUNCDESC_GOTOFFHI: howto manager. (line 496) -* BFD_RELOC_FRV_FUNCDESC_GOTOFFLO: howto manager. (line 497) -* BFD_RELOC_FRV_FUNCDESC_VALUE: howto manager. (line 494) -* BFD_RELOC_FRV_GETTLSOFF: howto manager. (line 501) -* BFD_RELOC_FRV_GETTLSOFF_RELAX: howto manager. (line 514) -* BFD_RELOC_FRV_GOT12: howto manager. (line 487) -* BFD_RELOC_FRV_GOTHI: howto manager. (line 488) -* BFD_RELOC_FRV_GOTLO: howto manager. (line 489) -* BFD_RELOC_FRV_GOTOFF12: howto manager. (line 498) -* BFD_RELOC_FRV_GOTOFFHI: howto manager. (line 499) -* BFD_RELOC_FRV_GOTOFFLO: howto manager. (line 500) -* BFD_RELOC_FRV_GOTTLSDESC12: howto manager. (line 503) -* BFD_RELOC_FRV_GOTTLSDESCHI: howto manager. (line 504) -* BFD_RELOC_FRV_GOTTLSDESCLO: howto manager. (line 505) -* BFD_RELOC_FRV_GOTTLSOFF12: howto manager. (line 509) -* BFD_RELOC_FRV_GOTTLSOFFHI: howto manager. (line 510) -* BFD_RELOC_FRV_GOTTLSOFFLO: howto manager. (line 511) -* BFD_RELOC_FRV_GPREL12: howto manager. (line 482) -* BFD_RELOC_FRV_GPREL32: howto manager. (line 484) -* BFD_RELOC_FRV_GPRELHI: howto manager. (line 485) -* BFD_RELOC_FRV_GPRELLO: howto manager. (line 486) -* BFD_RELOC_FRV_GPRELU12: howto manager. (line 483) -* BFD_RELOC_FRV_HI16: howto manager. (line 481) -* BFD_RELOC_FRV_LABEL16: howto manager. (line 478) -* BFD_RELOC_FRV_LABEL24: howto manager. (line 479) -* BFD_RELOC_FRV_LO16: howto manager. (line 480) -* BFD_RELOC_FRV_TLSDESC_RELAX: howto manager. (line 513) -* BFD_RELOC_FRV_TLSDESC_VALUE: howto manager. (line 502) -* BFD_RELOC_FRV_TLSMOFF: howto manager. (line 516) -* BFD_RELOC_FRV_TLSMOFF12: howto manager. (line 506) -* BFD_RELOC_FRV_TLSMOFFHI: howto manager. (line 507) -* BFD_RELOC_FRV_TLSMOFFLO: howto manager. (line 508) -* BFD_RELOC_FRV_TLSOFF: howto manager. (line 512) -* BFD_RELOC_FRV_TLSOFF_RELAX: howto manager. (line 515) +* BFD_RELOC_CR16_ABS20: howto manager. (line 2437) +* BFD_RELOC_CR16_ABS24: howto manager. (line 2438) +* BFD_RELOC_CR16_DISP16: howto manager. (line 2448) +* BFD_RELOC_CR16_DISP20: howto manager. (line 2449) +* BFD_RELOC_CR16_DISP24: howto manager. (line 2450) +* BFD_RELOC_CR16_DISP24a: howto manager. (line 2451) +* BFD_RELOC_CR16_DISP4: howto manager. (line 2446) +* BFD_RELOC_CR16_DISP8: howto manager. (line 2447) +* BFD_RELOC_CR16_GLOB_DAT: howto manager. (line 2457) +* BFD_RELOC_CR16_GOT_REGREL20: howto manager. (line 2455) +* BFD_RELOC_CR16_GOTC_REGREL20: howto manager. (line 2456) +* BFD_RELOC_CR16_IMM16: howto manager. (line 2441) +* BFD_RELOC_CR16_IMM20: howto manager. (line 2442) +* BFD_RELOC_CR16_IMM24: howto manager. (line 2443) +* BFD_RELOC_CR16_IMM32: howto manager. (line 2444) +* BFD_RELOC_CR16_IMM32a: howto manager. (line 2445) +* BFD_RELOC_CR16_IMM4: howto manager. (line 2439) +* BFD_RELOC_CR16_IMM8: howto manager. (line 2440) +* BFD_RELOC_CR16_NUM16: howto manager. (line 2426) +* BFD_RELOC_CR16_NUM32: howto manager. (line 2427) +* BFD_RELOC_CR16_NUM32a: howto manager. (line 2428) +* BFD_RELOC_CR16_NUM8: howto manager. (line 2425) +* BFD_RELOC_CR16_REGREL0: howto manager. (line 2429) +* BFD_RELOC_CR16_REGREL14: howto manager. (line 2432) +* BFD_RELOC_CR16_REGREL14a: howto manager. (line 2433) +* BFD_RELOC_CR16_REGREL16: howto manager. (line 2434) +* BFD_RELOC_CR16_REGREL20: howto manager. (line 2435) +* BFD_RELOC_CR16_REGREL20a: howto manager. (line 2436) +* BFD_RELOC_CR16_REGREL4: howto manager. (line 2430) +* BFD_RELOC_CR16_REGREL4a: howto manager. (line 2431) +* BFD_RELOC_CR16_SWITCH16: howto manager. (line 2453) +* BFD_RELOC_CR16_SWITCH32: howto manager. (line 2454) +* BFD_RELOC_CR16_SWITCH8: howto manager. (line 2452) +* BFD_RELOC_CRIS_16_DTPREL: howto manager. (line 2528) +* BFD_RELOC_CRIS_16_GOT: howto manager. (line 2504) +* BFD_RELOC_CRIS_16_GOT_GD: howto manager. (line 2524) +* BFD_RELOC_CRIS_16_GOT_TPREL: howto manager. (line 2530) +* BFD_RELOC_CRIS_16_GOTPLT: howto manager. (line 2510) +* BFD_RELOC_CRIS_16_TPREL: howto manager. (line 2532) +* BFD_RELOC_CRIS_32_DTPREL: howto manager. (line 2527) +* BFD_RELOC_CRIS_32_GD: howto manager. (line 2525) +* BFD_RELOC_CRIS_32_GOT: howto manager. (line 2501) +* BFD_RELOC_CRIS_32_GOT_GD: howto manager. (line 2523) +* BFD_RELOC_CRIS_32_GOT_TPREL: howto manager. (line 2529) +* BFD_RELOC_CRIS_32_GOTPLT: howto manager. (line 2507) +* BFD_RELOC_CRIS_32_GOTREL: howto manager. (line 2513) +* BFD_RELOC_CRIS_32_IE: howto manager. (line 2534) +* BFD_RELOC_CRIS_32_PLT_GOTREL: howto manager. (line 2516) +* BFD_RELOC_CRIS_32_PLT_PCREL: howto manager. (line 2519) +* BFD_RELOC_CRIS_32_TPREL: howto manager. (line 2531) +* BFD_RELOC_CRIS_BDISP8: howto manager. (line 2482) +* BFD_RELOC_CRIS_COPY: howto manager. (line 2495) +* BFD_RELOC_CRIS_DTP: howto manager. (line 2526) +* BFD_RELOC_CRIS_DTPMOD: howto manager. (line 2533) +* BFD_RELOC_CRIS_GLOB_DAT: howto manager. (line 2496) +* BFD_RELOC_CRIS_JUMP_SLOT: howto manager. (line 2497) +* BFD_RELOC_CRIS_LAPCQ_OFFSET: howto manager. (line 2490) +* BFD_RELOC_CRIS_RELATIVE: howto manager. (line 2498) +* BFD_RELOC_CRIS_SIGNED_16: howto manager. (line 2488) +* BFD_RELOC_CRIS_SIGNED_6: howto manager. (line 2484) +* BFD_RELOC_CRIS_SIGNED_8: howto manager. (line 2486) +* BFD_RELOC_CRIS_UNSIGNED_16: howto manager. (line 2489) +* BFD_RELOC_CRIS_UNSIGNED_4: howto manager. (line 2491) +* BFD_RELOC_CRIS_UNSIGNED_5: howto manager. (line 2483) +* BFD_RELOC_CRIS_UNSIGNED_6: howto manager. (line 2485) +* BFD_RELOC_CRIS_UNSIGNED_8: howto manager. (line 2487) +* BFD_RELOC_CRX_ABS16: howto manager. (line 2470) +* BFD_RELOC_CRX_ABS32: howto manager. (line 2471) +* BFD_RELOC_CRX_IMM16: howto manager. (line 2475) +* BFD_RELOC_CRX_IMM32: howto manager. (line 2476) +* BFD_RELOC_CRX_NUM16: howto manager. (line 2473) +* BFD_RELOC_CRX_NUM32: howto manager. (line 2474) +* BFD_RELOC_CRX_NUM8: howto manager. (line 2472) +* BFD_RELOC_CRX_REGREL12: howto manager. (line 2466) +* BFD_RELOC_CRX_REGREL22: howto manager. (line 2467) +* BFD_RELOC_CRX_REGREL28: howto manager. (line 2468) +* BFD_RELOC_CRX_REGREL32: howto manager. (line 2469) +* BFD_RELOC_CRX_REL16: howto manager. (line 2463) +* BFD_RELOC_CRX_REL24: howto manager. (line 2464) +* BFD_RELOC_CRX_REL32: howto manager. (line 2465) +* BFD_RELOC_CRX_REL4: howto manager. (line 2460) +* BFD_RELOC_CRX_REL8: howto manager. (line 2461) +* BFD_RELOC_CRX_REL8_CMP: howto manager. (line 2462) +* BFD_RELOC_CRX_SWITCH16: howto manager. (line 2478) +* BFD_RELOC_CRX_SWITCH32: howto manager. (line 2479) +* BFD_RELOC_CRX_SWITCH8: howto manager. (line 2477) +* BFD_RELOC_CTOR: howto manager. (line 783) +* BFD_RELOC_D10V_10_PCREL_L: howto manager. (line 1178) +* BFD_RELOC_D10V_10_PCREL_R: howto manager. (line 1174) +* BFD_RELOC_D10V_18: howto manager. (line 1183) +* BFD_RELOC_D10V_18_PCREL: howto manager. (line 1186) +* BFD_RELOC_D30V_15: howto manager. (line 1201) +* BFD_RELOC_D30V_15_PCREL: howto manager. (line 1205) +* BFD_RELOC_D30V_15_PCREL_R: howto manager. (line 1209) +* BFD_RELOC_D30V_21: howto manager. (line 1214) +* BFD_RELOC_D30V_21_PCREL: howto manager. (line 1218) +* BFD_RELOC_D30V_21_PCREL_R: howto manager. (line 1222) +* BFD_RELOC_D30V_32: howto manager. (line 1227) +* BFD_RELOC_D30V_32_PCREL: howto manager. (line 1230) +* BFD_RELOC_D30V_6: howto manager. (line 1189) +* BFD_RELOC_D30V_9_PCREL: howto manager. (line 1192) +* BFD_RELOC_D30V_9_PCREL_R: howto manager. (line 1196) +* BFD_RELOC_DLX_HI16_S: howto manager. (line 1233) +* BFD_RELOC_DLX_JMP26: howto manager. (line 1239) +* BFD_RELOC_DLX_LO16: howto manager. (line 1236) +* BFD_RELOC_EPIPHANY_HIGH: howto manager. (line 3411) +* BFD_RELOC_EPIPHANY_IMM11: howto manager. (line 3420) +* BFD_RELOC_EPIPHANY_IMM8: howto manager. (line 3424) +* BFD_RELOC_EPIPHANY_LOW: howto manager. (line 3414) +* BFD_RELOC_EPIPHANY_SIMM11: howto manager. (line 3417) +* BFD_RELOC_EPIPHANY_SIMM24: howto manager. (line 3408) +* BFD_RELOC_EPIPHANY_SIMM8: howto manager. (line 3405) +* BFD_RELOC_FR30_10_IN_8: howto manager. (line 1681) +* BFD_RELOC_FR30_12_PCREL: howto manager. (line 1689) +* BFD_RELOC_FR30_20: howto manager. (line 1665) +* BFD_RELOC_FR30_48: howto manager. (line 1662) +* BFD_RELOC_FR30_6_IN_4: howto manager. (line 1669) +* BFD_RELOC_FR30_8_IN_8: howto manager. (line 1673) +* BFD_RELOC_FR30_9_IN_8: howto manager. (line 1677) +* BFD_RELOC_FR30_9_PCREL: howto manager. (line 1685) +* BFD_RELOC_FRV_FUNCDESC: howto manager. (line 491) +* BFD_RELOC_FRV_FUNCDESC_GOT12: howto manager. (line 492) +* BFD_RELOC_FRV_FUNCDESC_GOTHI: howto manager. (line 493) +* BFD_RELOC_FRV_FUNCDESC_GOTLO: howto manager. (line 494) +* BFD_RELOC_FRV_FUNCDESC_GOTOFF12: howto manager. (line 496) +* BFD_RELOC_FRV_FUNCDESC_GOTOFFHI: howto manager. (line 497) +* BFD_RELOC_FRV_FUNCDESC_GOTOFFLO: howto manager. (line 498) +* BFD_RELOC_FRV_FUNCDESC_VALUE: howto manager. (line 495) +* BFD_RELOC_FRV_GETTLSOFF: howto manager. (line 502) +* BFD_RELOC_FRV_GETTLSOFF_RELAX: howto manager. (line 515) +* BFD_RELOC_FRV_GOT12: howto manager. (line 488) +* BFD_RELOC_FRV_GOTHI: howto manager. (line 489) +* BFD_RELOC_FRV_GOTLO: howto manager. (line 490) +* BFD_RELOC_FRV_GOTOFF12: howto manager. (line 499) +* BFD_RELOC_FRV_GOTOFFHI: howto manager. (line 500) +* BFD_RELOC_FRV_GOTOFFLO: howto manager. (line 501) +* BFD_RELOC_FRV_GOTTLSDESC12: howto manager. (line 504) +* BFD_RELOC_FRV_GOTTLSDESCHI: howto manager. (line 505) +* BFD_RELOC_FRV_GOTTLSDESCLO: howto manager. (line 506) +* BFD_RELOC_FRV_GOTTLSOFF12: howto manager. (line 510) +* BFD_RELOC_FRV_GOTTLSOFFHI: howto manager. (line 511) +* BFD_RELOC_FRV_GOTTLSOFFLO: howto manager. (line 512) +* BFD_RELOC_FRV_GPREL12: howto manager. (line 483) +* BFD_RELOC_FRV_GPREL32: howto manager. (line 485) +* BFD_RELOC_FRV_GPRELHI: howto manager. (line 486) +* BFD_RELOC_FRV_GPRELLO: howto manager. (line 487) +* BFD_RELOC_FRV_GPRELU12: howto manager. (line 484) +* BFD_RELOC_FRV_HI16: howto manager. (line 482) +* BFD_RELOC_FRV_LABEL16: howto manager. (line 479) +* BFD_RELOC_FRV_LABEL24: howto manager. (line 480) +* BFD_RELOC_FRV_LO16: howto manager. (line 481) +* BFD_RELOC_FRV_TLSDESC_RELAX: howto manager. (line 514) +* BFD_RELOC_FRV_TLSDESC_VALUE: howto manager. (line 503) +* BFD_RELOC_FRV_TLSMOFF: howto manager. (line 517) +* BFD_RELOC_FRV_TLSMOFF12: howto manager. (line 507) +* BFD_RELOC_FRV_TLSMOFFHI: howto manager. (line 508) +* BFD_RELOC_FRV_TLSMOFFLO: howto manager. (line 509) +* BFD_RELOC_FRV_TLSOFF: howto manager. (line 513) +* BFD_RELOC_FRV_TLSOFF_RELAX: howto manager. (line 516) * BFD_RELOC_GPREL16: howto manager. (line 125) * BFD_RELOC_GPREL32: howto manager. (line 126) -* BFD_RELOC_H8_DIR16A8: howto manager. (line 2381) -* BFD_RELOC_H8_DIR16R8: howto manager. (line 2382) -* BFD_RELOC_H8_DIR24A8: howto manager. (line 2383) -* BFD_RELOC_H8_DIR24R8: howto manager. (line 2384) -* BFD_RELOC_H8_DIR32A16: howto manager. (line 2385) -* BFD_RELOC_H8_DISP32A16: howto manager. (line 2386) +* BFD_RELOC_H8_DIR16A8: howto manager. (line 2575) +* BFD_RELOC_H8_DIR16R8: howto manager. (line 2576) +* BFD_RELOC_H8_DIR24A8: howto manager. (line 2577) +* BFD_RELOC_H8_DIR24R8: howto manager. (line 2578) +* BFD_RELOC_H8_DIR32A16: howto manager. (line 2579) +* BFD_RELOC_H8_DISP32A16: howto manager. (line 2580) * BFD_RELOC_HI16: howto manager. (line 352) * BFD_RELOC_HI16_BASEREL: howto manager. (line 101) * BFD_RELOC_HI16_GOTOFF: howto manager. (line 57) @@ -11761,257 +12141,257 @@ BFD Index * BFD_RELOC_HI16_S_PCREL: howto manager. (line 367) * BFD_RELOC_HI16_S_PLTOFF: howto manager. (line 70) * BFD_RELOC_HI22: howto manager. (line 120) -* BFD_RELOC_I370_D12: howto manager. (line 771) +* BFD_RELOC_I370_D12: howto manager. (line 780) * BFD_RELOC_I960_CALLJ: howto manager. (line 132) -* BFD_RELOC_IA64_COPY: howto manager. (line 2063) -* BFD_RELOC_IA64_DIR32LSB: howto manager. (line 2008) -* BFD_RELOC_IA64_DIR32MSB: howto manager. (line 2007) -* BFD_RELOC_IA64_DIR64LSB: howto manager. (line 2010) -* BFD_RELOC_IA64_DIR64MSB: howto manager. (line 2009) -* BFD_RELOC_IA64_DTPMOD64LSB: howto manager. (line 2073) -* BFD_RELOC_IA64_DTPMOD64MSB: howto manager. (line 2072) -* BFD_RELOC_IA64_DTPREL14: howto manager. (line 2075) -* BFD_RELOC_IA64_DTPREL22: howto manager. (line 2076) -* BFD_RELOC_IA64_DTPREL32LSB: howto manager. (line 2079) -* BFD_RELOC_IA64_DTPREL32MSB: howto manager. (line 2078) -* BFD_RELOC_IA64_DTPREL64I: howto manager. (line 2077) -* BFD_RELOC_IA64_DTPREL64LSB: howto manager. (line 2081) -* BFD_RELOC_IA64_DTPREL64MSB: howto manager. (line 2080) -* BFD_RELOC_IA64_FPTR32LSB: howto manager. (line 2025) -* BFD_RELOC_IA64_FPTR32MSB: howto manager. (line 2024) -* BFD_RELOC_IA64_FPTR64I: howto manager. (line 2023) -* BFD_RELOC_IA64_FPTR64LSB: howto manager. (line 2027) -* BFD_RELOC_IA64_FPTR64MSB: howto manager. (line 2026) -* BFD_RELOC_IA64_GPREL22: howto manager. (line 2011) -* BFD_RELOC_IA64_GPREL32LSB: howto manager. (line 2014) -* BFD_RELOC_IA64_GPREL32MSB: howto manager. (line 2013) -* BFD_RELOC_IA64_GPREL64I: howto manager. (line 2012) -* BFD_RELOC_IA64_GPREL64LSB: howto manager. (line 2016) -* BFD_RELOC_IA64_GPREL64MSB: howto manager. (line 2015) -* BFD_RELOC_IA64_IMM14: howto manager. (line 2004) -* BFD_RELOC_IA64_IMM22: howto manager. (line 2005) -* BFD_RELOC_IA64_IMM64: howto manager. (line 2006) -* BFD_RELOC_IA64_IPLTLSB: howto manager. (line 2062) -* BFD_RELOC_IA64_IPLTMSB: howto manager. (line 2061) -* BFD_RELOC_IA64_LDXMOV: howto manager. (line 2065) -* BFD_RELOC_IA64_LTOFF22: howto manager. (line 2017) -* BFD_RELOC_IA64_LTOFF22X: howto manager. (line 2064) -* BFD_RELOC_IA64_LTOFF64I: howto manager. (line 2018) -* BFD_RELOC_IA64_LTOFF_DTPMOD22: howto manager. (line 2074) -* BFD_RELOC_IA64_LTOFF_DTPREL22: howto manager. (line 2082) -* BFD_RELOC_IA64_LTOFF_FPTR22: howto manager. (line 2039) -* BFD_RELOC_IA64_LTOFF_FPTR32LSB: howto manager. (line 2042) -* BFD_RELOC_IA64_LTOFF_FPTR32MSB: howto manager. (line 2041) -* BFD_RELOC_IA64_LTOFF_FPTR64I: howto manager. (line 2040) -* BFD_RELOC_IA64_LTOFF_FPTR64LSB: howto manager. (line 2044) -* BFD_RELOC_IA64_LTOFF_FPTR64MSB: howto manager. (line 2043) -* BFD_RELOC_IA64_LTOFF_TPREL22: howto manager. (line 2071) -* BFD_RELOC_IA64_LTV32LSB: howto manager. (line 2058) -* BFD_RELOC_IA64_LTV32MSB: howto manager. (line 2057) -* BFD_RELOC_IA64_LTV64LSB: howto manager. (line 2060) -* BFD_RELOC_IA64_LTV64MSB: howto manager. (line 2059) -* BFD_RELOC_IA64_PCREL21B: howto manager. (line 2028) -* BFD_RELOC_IA64_PCREL21BI: howto manager. (line 2029) -* BFD_RELOC_IA64_PCREL21F: howto manager. (line 2031) -* BFD_RELOC_IA64_PCREL21M: howto manager. (line 2030) -* BFD_RELOC_IA64_PCREL22: howto manager. (line 2032) -* BFD_RELOC_IA64_PCREL32LSB: howto manager. (line 2036) -* BFD_RELOC_IA64_PCREL32MSB: howto manager. (line 2035) -* BFD_RELOC_IA64_PCREL60B: howto manager. (line 2033) -* BFD_RELOC_IA64_PCREL64I: howto manager. (line 2034) -* BFD_RELOC_IA64_PCREL64LSB: howto manager. (line 2038) -* BFD_RELOC_IA64_PCREL64MSB: howto manager. (line 2037) -* BFD_RELOC_IA64_PLTOFF22: howto manager. (line 2019) -* BFD_RELOC_IA64_PLTOFF64I: howto manager. (line 2020) -* BFD_RELOC_IA64_PLTOFF64LSB: howto manager. (line 2022) -* BFD_RELOC_IA64_PLTOFF64MSB: howto manager. (line 2021) -* BFD_RELOC_IA64_REL32LSB: howto manager. (line 2054) -* BFD_RELOC_IA64_REL32MSB: howto manager. (line 2053) -* BFD_RELOC_IA64_REL64LSB: howto manager. (line 2056) -* BFD_RELOC_IA64_REL64MSB: howto manager. (line 2055) -* BFD_RELOC_IA64_SECREL32LSB: howto manager. (line 2050) -* BFD_RELOC_IA64_SECREL32MSB: howto manager. (line 2049) -* BFD_RELOC_IA64_SECREL64LSB: howto manager. (line 2052) -* BFD_RELOC_IA64_SECREL64MSB: howto manager. (line 2051) -* BFD_RELOC_IA64_SEGREL32LSB: howto manager. (line 2046) -* BFD_RELOC_IA64_SEGREL32MSB: howto manager. (line 2045) -* BFD_RELOC_IA64_SEGREL64LSB: howto manager. (line 2048) -* BFD_RELOC_IA64_SEGREL64MSB: howto manager. (line 2047) -* BFD_RELOC_IA64_TPREL14: howto manager. (line 2066) -* BFD_RELOC_IA64_TPREL22: howto manager. (line 2067) -* BFD_RELOC_IA64_TPREL64I: howto manager. (line 2068) -* BFD_RELOC_IA64_TPREL64LSB: howto manager. (line 2070) -* BFD_RELOC_IA64_TPREL64MSB: howto manager. (line 2069) -* BFD_RELOC_IP2K_ADDR16CJP: howto manager. (line 1956) -* BFD_RELOC_IP2K_BANK: howto manager. (line 1953) -* BFD_RELOC_IP2K_EX8DATA: howto manager. (line 1964) -* BFD_RELOC_IP2K_FR9: howto manager. (line 1950) -* BFD_RELOC_IP2K_FR_OFFSET: howto manager. (line 1977) -* BFD_RELOC_IP2K_HI8DATA: howto manager. (line 1963) -* BFD_RELOC_IP2K_HI8INSN: howto manager. (line 1968) -* BFD_RELOC_IP2K_LO8DATA: howto manager. (line 1962) -* BFD_RELOC_IP2K_LO8INSN: howto manager. (line 1967) -* BFD_RELOC_IP2K_PAGE3: howto manager. (line 1959) -* BFD_RELOC_IP2K_PC_SKIP: howto manager. (line 1971) -* BFD_RELOC_IP2K_TEXT: howto manager. (line 1974) -* BFD_RELOC_IQ2000_OFFSET_16: howto manager. (line 2472) -* BFD_RELOC_IQ2000_OFFSET_21: howto manager. (line 2473) -* BFD_RELOC_IQ2000_UHI16: howto manager. (line 2474) -* BFD_RELOC_LM32_16_GOT: howto manager. (line 2579) -* BFD_RELOC_LM32_BRANCH: howto manager. (line 2578) -* BFD_RELOC_LM32_CALL: howto manager. (line 2577) -* BFD_RELOC_LM32_COPY: howto manager. (line 2582) -* BFD_RELOC_LM32_GLOB_DAT: howto manager. (line 2583) -* BFD_RELOC_LM32_GOTOFF_HI16: howto manager. (line 2580) -* BFD_RELOC_LM32_GOTOFF_LO16: howto manager. (line 2581) -* BFD_RELOC_LM32_JMP_SLOT: howto manager. (line 2584) -* BFD_RELOC_LM32_RELATIVE: howto manager. (line 2585) +* BFD_RELOC_IA64_COPY: howto manager. (line 2257) +* BFD_RELOC_IA64_DIR32LSB: howto manager. (line 2202) +* BFD_RELOC_IA64_DIR32MSB: howto manager. (line 2201) +* BFD_RELOC_IA64_DIR64LSB: howto manager. (line 2204) +* BFD_RELOC_IA64_DIR64MSB: howto manager. (line 2203) +* BFD_RELOC_IA64_DTPMOD64LSB: howto manager. (line 2267) +* BFD_RELOC_IA64_DTPMOD64MSB: howto manager. (line 2266) +* BFD_RELOC_IA64_DTPREL14: howto manager. (line 2269) +* BFD_RELOC_IA64_DTPREL22: howto manager. (line 2270) +* BFD_RELOC_IA64_DTPREL32LSB: howto manager. (line 2273) +* BFD_RELOC_IA64_DTPREL32MSB: howto manager. (line 2272) +* BFD_RELOC_IA64_DTPREL64I: howto manager. (line 2271) +* BFD_RELOC_IA64_DTPREL64LSB: howto manager. (line 2275) +* BFD_RELOC_IA64_DTPREL64MSB: howto manager. (line 2274) +* BFD_RELOC_IA64_FPTR32LSB: howto manager. (line 2219) +* BFD_RELOC_IA64_FPTR32MSB: howto manager. (line 2218) +* BFD_RELOC_IA64_FPTR64I: howto manager. (line 2217) +* BFD_RELOC_IA64_FPTR64LSB: howto manager. (line 2221) +* BFD_RELOC_IA64_FPTR64MSB: howto manager. (line 2220) +* BFD_RELOC_IA64_GPREL22: howto manager. (line 2205) +* BFD_RELOC_IA64_GPREL32LSB: howto manager. (line 2208) +* BFD_RELOC_IA64_GPREL32MSB: howto manager. (line 2207) +* BFD_RELOC_IA64_GPREL64I: howto manager. (line 2206) +* BFD_RELOC_IA64_GPREL64LSB: howto manager. (line 2210) +* BFD_RELOC_IA64_GPREL64MSB: howto manager. (line 2209) +* BFD_RELOC_IA64_IMM14: howto manager. (line 2198) +* BFD_RELOC_IA64_IMM22: howto manager. (line 2199) +* BFD_RELOC_IA64_IMM64: howto manager. (line 2200) +* BFD_RELOC_IA64_IPLTLSB: howto manager. (line 2256) +* BFD_RELOC_IA64_IPLTMSB: howto manager. (line 2255) +* BFD_RELOC_IA64_LDXMOV: howto manager. (line 2259) +* BFD_RELOC_IA64_LTOFF22: howto manager. (line 2211) +* BFD_RELOC_IA64_LTOFF22X: howto manager. (line 2258) +* BFD_RELOC_IA64_LTOFF64I: howto manager. (line 2212) +* BFD_RELOC_IA64_LTOFF_DTPMOD22: howto manager. (line 2268) +* BFD_RELOC_IA64_LTOFF_DTPREL22: howto manager. (line 2276) +* BFD_RELOC_IA64_LTOFF_FPTR22: howto manager. (line 2233) +* BFD_RELOC_IA64_LTOFF_FPTR32LSB: howto manager. (line 2236) +* BFD_RELOC_IA64_LTOFF_FPTR32MSB: howto manager. (line 2235) +* BFD_RELOC_IA64_LTOFF_FPTR64I: howto manager. (line 2234) +* BFD_RELOC_IA64_LTOFF_FPTR64LSB: howto manager. (line 2238) +* BFD_RELOC_IA64_LTOFF_FPTR64MSB: howto manager. (line 2237) +* BFD_RELOC_IA64_LTOFF_TPREL22: howto manager. (line 2265) +* BFD_RELOC_IA64_LTV32LSB: howto manager. (line 2252) +* BFD_RELOC_IA64_LTV32MSB: howto manager. (line 2251) +* BFD_RELOC_IA64_LTV64LSB: howto manager. (line 2254) +* BFD_RELOC_IA64_LTV64MSB: howto manager. (line 2253) +* BFD_RELOC_IA64_PCREL21B: howto manager. (line 2222) +* BFD_RELOC_IA64_PCREL21BI: howto manager. (line 2223) +* BFD_RELOC_IA64_PCREL21F: howto manager. (line 2225) +* BFD_RELOC_IA64_PCREL21M: howto manager. (line 2224) +* BFD_RELOC_IA64_PCREL22: howto manager. (line 2226) +* BFD_RELOC_IA64_PCREL32LSB: howto manager. (line 2230) +* BFD_RELOC_IA64_PCREL32MSB: howto manager. (line 2229) +* BFD_RELOC_IA64_PCREL60B: howto manager. (line 2227) +* BFD_RELOC_IA64_PCREL64I: howto manager. (line 2228) +* BFD_RELOC_IA64_PCREL64LSB: howto manager. (line 2232) +* BFD_RELOC_IA64_PCREL64MSB: howto manager. (line 2231) +* BFD_RELOC_IA64_PLTOFF22: howto manager. (line 2213) +* BFD_RELOC_IA64_PLTOFF64I: howto manager. (line 2214) +* BFD_RELOC_IA64_PLTOFF64LSB: howto manager. (line 2216) +* BFD_RELOC_IA64_PLTOFF64MSB: howto manager. (line 2215) +* BFD_RELOC_IA64_REL32LSB: howto manager. (line 2248) +* BFD_RELOC_IA64_REL32MSB: howto manager. (line 2247) +* BFD_RELOC_IA64_REL64LSB: howto manager. (line 2250) +* BFD_RELOC_IA64_REL64MSB: howto manager. (line 2249) +* BFD_RELOC_IA64_SECREL32LSB: howto manager. (line 2244) +* BFD_RELOC_IA64_SECREL32MSB: howto manager. (line 2243) +* BFD_RELOC_IA64_SECREL64LSB: howto manager. (line 2246) +* BFD_RELOC_IA64_SECREL64MSB: howto manager. (line 2245) +* BFD_RELOC_IA64_SEGREL32LSB: howto manager. (line 2240) +* BFD_RELOC_IA64_SEGREL32MSB: howto manager. (line 2239) +* BFD_RELOC_IA64_SEGREL64LSB: howto manager. (line 2242) +* BFD_RELOC_IA64_SEGREL64MSB: howto manager. (line 2241) +* BFD_RELOC_IA64_TPREL14: howto manager. (line 2260) +* BFD_RELOC_IA64_TPREL22: howto manager. (line 2261) +* BFD_RELOC_IA64_TPREL64I: howto manager. (line 2262) +* BFD_RELOC_IA64_TPREL64LSB: howto manager. (line 2264) +* BFD_RELOC_IA64_TPREL64MSB: howto manager. (line 2263) +* BFD_RELOC_IP2K_ADDR16CJP: howto manager. (line 2150) +* BFD_RELOC_IP2K_BANK: howto manager. (line 2147) +* BFD_RELOC_IP2K_EX8DATA: howto manager. (line 2158) +* BFD_RELOC_IP2K_FR9: howto manager. (line 2144) +* BFD_RELOC_IP2K_FR_OFFSET: howto manager. (line 2171) +* BFD_RELOC_IP2K_HI8DATA: howto manager. (line 2157) +* BFD_RELOC_IP2K_HI8INSN: howto manager. (line 2162) +* BFD_RELOC_IP2K_LO8DATA: howto manager. (line 2156) +* BFD_RELOC_IP2K_LO8INSN: howto manager. (line 2161) +* BFD_RELOC_IP2K_PAGE3: howto manager. (line 2153) +* BFD_RELOC_IP2K_PC_SKIP: howto manager. (line 2165) +* BFD_RELOC_IP2K_TEXT: howto manager. (line 2168) +* BFD_RELOC_IQ2000_OFFSET_16: howto manager. (line 2681) +* BFD_RELOC_IQ2000_OFFSET_21: howto manager. (line 2682) +* BFD_RELOC_IQ2000_UHI16: howto manager. (line 2683) +* BFD_RELOC_LM32_16_GOT: howto manager. (line 2788) +* BFD_RELOC_LM32_BRANCH: howto manager. (line 2787) +* BFD_RELOC_LM32_CALL: howto manager. (line 2786) +* BFD_RELOC_LM32_COPY: howto manager. (line 2791) +* BFD_RELOC_LM32_GLOB_DAT: howto manager. (line 2792) +* BFD_RELOC_LM32_GOTOFF_HI16: howto manager. (line 2789) +* BFD_RELOC_LM32_GOTOFF_LO16: howto manager. (line 2790) +* BFD_RELOC_LM32_JMP_SLOT: howto manager. (line 2793) +* BFD_RELOC_LM32_RELATIVE: howto manager. (line 2794) * BFD_RELOC_LO10: howto manager. (line 121) * BFD_RELOC_LO16: howto manager. (line 361) * BFD_RELOC_LO16_BASEREL: howto manager. (line 100) * BFD_RELOC_LO16_GOTOFF: howto manager. (line 56) * BFD_RELOC_LO16_PCREL: howto manager. (line 370) * BFD_RELOC_LO16_PLTOFF: howto manager. (line 68) -* BFD_RELOC_M32C_HI8: howto manager. (line 1233) -* BFD_RELOC_M32C_RL_1ADDR: howto manager. (line 1235) -* BFD_RELOC_M32C_RL_2ADDR: howto manager. (line 1236) -* BFD_RELOC_M32C_RL_JUMP: howto manager. (line 1234) -* BFD_RELOC_M32R_10_PCREL: howto manager. (line 1243) -* BFD_RELOC_M32R_18_PCREL: howto manager. (line 1247) -* BFD_RELOC_M32R_24: howto manager. (line 1239) -* BFD_RELOC_M32R_26_PCREL: howto manager. (line 1250) -* BFD_RELOC_M32R_26_PLTREL: howto manager. (line 1269) -* BFD_RELOC_M32R_COPY: howto manager. (line 1270) -* BFD_RELOC_M32R_GLOB_DAT: howto manager. (line 1271) -* BFD_RELOC_M32R_GOT16_HI_SLO: howto manager. (line 1280) -* BFD_RELOC_M32R_GOT16_HI_ULO: howto manager. (line 1279) -* BFD_RELOC_M32R_GOT16_LO: howto manager. (line 1281) -* BFD_RELOC_M32R_GOT24: howto manager. (line 1268) -* BFD_RELOC_M32R_GOTOFF: howto manager. (line 1274) -* BFD_RELOC_M32R_GOTOFF_HI_SLO: howto manager. (line 1276) -* BFD_RELOC_M32R_GOTOFF_HI_ULO: howto manager. (line 1275) -* BFD_RELOC_M32R_GOTOFF_LO: howto manager. (line 1277) -* BFD_RELOC_M32R_GOTPC24: howto manager. (line 1278) -* BFD_RELOC_M32R_GOTPC_HI_SLO: howto manager. (line 1283) -* BFD_RELOC_M32R_GOTPC_HI_ULO: howto manager. (line 1282) -* BFD_RELOC_M32R_GOTPC_LO: howto manager. (line 1284) -* BFD_RELOC_M32R_HI16_SLO: howto manager. (line 1257) -* BFD_RELOC_M32R_HI16_ULO: howto manager. (line 1253) -* BFD_RELOC_M32R_JMP_SLOT: howto manager. (line 1272) -* BFD_RELOC_M32R_LO16: howto manager. (line 1261) -* BFD_RELOC_M32R_RELATIVE: howto manager. (line 1273) -* BFD_RELOC_M32R_SDA16: howto manager. (line 1264) -* BFD_RELOC_M68HC11_24: howto manager. (line 2118) -* BFD_RELOC_M68HC11_3B: howto manager. (line 2093) -* BFD_RELOC_M68HC11_HI8: howto manager. (line 2085) -* BFD_RELOC_M68HC11_LO16: howto manager. (line 2107) -* BFD_RELOC_M68HC11_LO8: howto manager. (line 2089) -* BFD_RELOC_M68HC11_PAGE: howto manager. (line 2113) -* BFD_RELOC_M68HC11_RL_GROUP: howto manager. (line 2102) -* BFD_RELOC_M68HC11_RL_JUMP: howto manager. (line 2096) -* BFD_RELOC_M68HC12_10_PCREL: howto manager. (line 2178) -* BFD_RELOC_M68HC12_16B: howto manager. (line 2172) -* BFD_RELOC_M68HC12_5B: howto manager. (line 2124) -* BFD_RELOC_M68HC12_9_PCREL: howto manager. (line 2175) -* BFD_RELOC_M68HC12_9B: howto manager. (line 2169) -* BFD_RELOC_M68HC12_HI8XG: howto manager. (line 2185) -* BFD_RELOC_M68HC12_LO8XG: howto manager. (line 2181) -* BFD_RELOC_MACH_O_LOCAL_SECTDIFF: howto manager. (line 2592) -* BFD_RELOC_MACH_O_PAIR: howto manager. (line 2595) -* BFD_RELOC_MACH_O_SECTDIFF: howto manager. (line 2588) -* BFD_RELOC_MACH_O_X86_64_BRANCH32: howto manager. (line 2598) -* BFD_RELOC_MACH_O_X86_64_BRANCH8: howto manager. (line 2599) -* BFD_RELOC_MACH_O_X86_64_GOT: howto manager. (line 2603) -* BFD_RELOC_MACH_O_X86_64_GOT_LOAD: howto manager. (line 2606) -* BFD_RELOC_MACH_O_X86_64_PCREL32_1: howto manager. (line 2616) -* BFD_RELOC_MACH_O_X86_64_PCREL32_2: howto manager. (line 2619) -* BFD_RELOC_MACH_O_X86_64_PCREL32_4: howto manager. (line 2622) -* BFD_RELOC_MACH_O_X86_64_SUBTRACTOR32: howto manager. (line 2610) -* BFD_RELOC_MACH_O_X86_64_SUBTRACTOR64: howto manager. (line 2613) -* BFD_RELOC_MCORE_PCREL_32: howto manager. (line 1514) -* BFD_RELOC_MCORE_PCREL_IMM11BY2: howto manager. (line 1512) -* BFD_RELOC_MCORE_PCREL_IMM4BY2: howto manager. (line 1513) -* BFD_RELOC_MCORE_PCREL_IMM8BY4: howto manager. (line 1511) -* BFD_RELOC_MCORE_PCREL_JSR_IMM11BY2: howto manager. (line 1515) -* BFD_RELOC_MCORE_RVA: howto manager. (line 1516) -* BFD_RELOC_MEP_16: howto manager. (line 1520) -* BFD_RELOC_MEP_32: howto manager. (line 1521) -* BFD_RELOC_MEP_8: howto manager. (line 1519) -* BFD_RELOC_MEP_ADDR24A4: howto manager. (line 1536) -* BFD_RELOC_MEP_GNU_VTENTRY: howto manager. (line 1538) -* BFD_RELOC_MEP_GNU_VTINHERIT: howto manager. (line 1537) -* BFD_RELOC_MEP_GPREL: howto manager. (line 1530) -* BFD_RELOC_MEP_HI16S: howto manager. (line 1529) -* BFD_RELOC_MEP_HI16U: howto manager. (line 1528) -* BFD_RELOC_MEP_LOW16: howto manager. (line 1527) -* BFD_RELOC_MEP_PCABS24A2: howto manager. (line 1526) -* BFD_RELOC_MEP_PCREL12A2: howto manager. (line 1523) -* BFD_RELOC_MEP_PCREL17A2: howto manager. (line 1524) -* BFD_RELOC_MEP_PCREL24A2: howto manager. (line 1525) -* BFD_RELOC_MEP_PCREL8A2: howto manager. (line 1522) -* BFD_RELOC_MEP_TPREL: howto manager. (line 1531) -* BFD_RELOC_MEP_TPREL7: howto manager. (line 1532) -* BFD_RELOC_MEP_TPREL7A2: howto manager. (line 1533) -* BFD_RELOC_MEP_TPREL7A4: howto manager. (line 1534) -* BFD_RELOC_MEP_UIMM24: howto manager. (line 1535) -* BFD_RELOC_METAG_COPY: howto manager. (line 1560) -* BFD_RELOC_METAG_GETSET_GOT: howto manager. (line 1552) -* BFD_RELOC_METAG_GETSET_GOTOFF: howto manager. (line 1551) -* BFD_RELOC_METAG_GETSETOFF: howto manager. (line 1544) -* BFD_RELOC_METAG_GLOB_DAT: howto manager. (line 1563) -* BFD_RELOC_METAG_GOTOFF: howto manager. (line 1558) -* BFD_RELOC_METAG_HI16_GOTOFF: howto manager. (line 1549) -* BFD_RELOC_METAG_HI16_GOTPC: howto manager. (line 1553) -* BFD_RELOC_METAG_HI16_PLT: howto manager. (line 1555) -* BFD_RELOC_METAG_HIADDR16: howto manager. (line 1541) -* BFD_RELOC_METAG_HIOG: howto manager. (line 1545) -* BFD_RELOC_METAG_JMP_SLOT: howto manager. (line 1561) -* BFD_RELOC_METAG_LO16_GOTOFF: howto manager. (line 1550) -* BFD_RELOC_METAG_LO16_GOTPC: howto manager. (line 1554) -* BFD_RELOC_METAG_LO16_PLT: howto manager. (line 1556) -* BFD_RELOC_METAG_LOADDR16: howto manager. (line 1542) -* BFD_RELOC_METAG_LOOG: howto manager. (line 1546) -* BFD_RELOC_METAG_PLT: howto manager. (line 1559) -* BFD_RELOC_METAG_REL16: howto manager. (line 1548) -* BFD_RELOC_METAG_REL8: howto manager. (line 1547) -* BFD_RELOC_METAG_RELATIVE: howto manager. (line 1562) -* BFD_RELOC_METAG_RELBRANCH: howto manager. (line 1543) -* BFD_RELOC_METAG_RELBRANCH_PLT: howto manager. (line 1557) -* BFD_RELOC_METAG_TLS_DTPMOD: howto manager. (line 1574) -* BFD_RELOC_METAG_TLS_DTPOFF: howto manager. (line 1575) -* BFD_RELOC_METAG_TLS_GD: howto manager. (line 1564) -* BFD_RELOC_METAG_TLS_IE: howto manager. (line 1569) -* BFD_RELOC_METAG_TLS_IENONPIC: howto manager. (line 1570) -* BFD_RELOC_METAG_TLS_IENONPIC_HI16: howto manager. (line 1571) -* BFD_RELOC_METAG_TLS_IENONPIC_LO16: howto manager. (line 1572) -* BFD_RELOC_METAG_TLS_LDM: howto manager. (line 1565) -* BFD_RELOC_METAG_TLS_LDO: howto manager. (line 1568) -* BFD_RELOC_METAG_TLS_LDO_HI16: howto manager. (line 1566) -* BFD_RELOC_METAG_TLS_LDO_LO16: howto manager. (line 1567) -* BFD_RELOC_METAG_TLS_LE: howto manager. (line 1576) -* BFD_RELOC_METAG_TLS_LE_HI16: howto manager. (line 1577) -* BFD_RELOC_METAG_TLS_LE_LO16: howto manager. (line 1578) -* BFD_RELOC_METAG_TLS_TPOFF: howto manager. (line 1573) -* BFD_RELOC_MICROBLAZE_32_GOTOFF: howto manager. (line 2669) -* BFD_RELOC_MICROBLAZE_32_LO: howto manager. (line 2625) -* BFD_RELOC_MICROBLAZE_32_LO_PCREL: howto manager. (line 2629) -* BFD_RELOC_MICROBLAZE_32_ROSDA: howto manager. (line 2633) -* BFD_RELOC_MICROBLAZE_32_RWSDA: howto manager. (line 2637) -* BFD_RELOC_MICROBLAZE_32_SYM_OP_SYM: howto manager. (line 2641) -* BFD_RELOC_MICROBLAZE_32_TLSDTPMOD: howto manager. (line 2690) -* BFD_RELOC_MICROBLAZE_32_TLSDTPREL: howto manager. (line 2693) -* BFD_RELOC_MICROBLAZE_64_GOT: howto manager. (line 2655) -* BFD_RELOC_MICROBLAZE_64_GOTOFF: howto manager. (line 2664) -* BFD_RELOC_MICROBLAZE_64_GOTPC: howto manager. (line 2650) -* BFD_RELOC_MICROBLAZE_64_NONE: howto manager. (line 2645) -* BFD_RELOC_MICROBLAZE_64_PLT: howto manager. (line 2659) -* BFD_RELOC_MICROBLAZE_64_TLS: howto manager. (line 2677) -* BFD_RELOC_MICROBLAZE_64_TLSDTPREL: howto manager. (line 2696) -* BFD_RELOC_MICROBLAZE_64_TLSGD: howto manager. (line 2680) -* BFD_RELOC_MICROBLAZE_64_TLSGOTTPREL: howto manager. (line 2700) -* BFD_RELOC_MICROBLAZE_64_TLSLD: howto manager. (line 2685) -* BFD_RELOC_MICROBLAZE_64_TLSTPREL: howto manager. (line 2704) -* BFD_RELOC_MICROBLAZE_COPY: howto manager. (line 2673) +* BFD_RELOC_M32C_HI8: howto manager. (line 1242) +* BFD_RELOC_M32C_RL_1ADDR: howto manager. (line 1244) +* BFD_RELOC_M32C_RL_2ADDR: howto manager. (line 1245) +* BFD_RELOC_M32C_RL_JUMP: howto manager. (line 1243) +* BFD_RELOC_M32R_10_PCREL: howto manager. (line 1252) +* BFD_RELOC_M32R_18_PCREL: howto manager. (line 1256) +* BFD_RELOC_M32R_24: howto manager. (line 1248) +* BFD_RELOC_M32R_26_PCREL: howto manager. (line 1259) +* BFD_RELOC_M32R_26_PLTREL: howto manager. (line 1278) +* BFD_RELOC_M32R_COPY: howto manager. (line 1279) +* BFD_RELOC_M32R_GLOB_DAT: howto manager. (line 1280) +* BFD_RELOC_M32R_GOT16_HI_SLO: howto manager. (line 1289) +* BFD_RELOC_M32R_GOT16_HI_ULO: howto manager. (line 1288) +* BFD_RELOC_M32R_GOT16_LO: howto manager. (line 1290) +* BFD_RELOC_M32R_GOT24: howto manager. (line 1277) +* BFD_RELOC_M32R_GOTOFF: howto manager. (line 1283) +* BFD_RELOC_M32R_GOTOFF_HI_SLO: howto manager. (line 1285) +* BFD_RELOC_M32R_GOTOFF_HI_ULO: howto manager. (line 1284) +* BFD_RELOC_M32R_GOTOFF_LO: howto manager. (line 1286) +* BFD_RELOC_M32R_GOTPC24: howto manager. (line 1287) +* BFD_RELOC_M32R_GOTPC_HI_SLO: howto manager. (line 1292) +* BFD_RELOC_M32R_GOTPC_HI_ULO: howto manager. (line 1291) +* BFD_RELOC_M32R_GOTPC_LO: howto manager. (line 1293) +* BFD_RELOC_M32R_HI16_SLO: howto manager. (line 1266) +* BFD_RELOC_M32R_HI16_ULO: howto manager. (line 1262) +* BFD_RELOC_M32R_JMP_SLOT: howto manager. (line 1281) +* BFD_RELOC_M32R_LO16: howto manager. (line 1270) +* BFD_RELOC_M32R_RELATIVE: howto manager. (line 1282) +* BFD_RELOC_M32R_SDA16: howto manager. (line 1273) +* BFD_RELOC_M68HC11_24: howto manager. (line 2312) +* BFD_RELOC_M68HC11_3B: howto manager. (line 2287) +* BFD_RELOC_M68HC11_HI8: howto manager. (line 2279) +* BFD_RELOC_M68HC11_LO16: howto manager. (line 2301) +* BFD_RELOC_M68HC11_LO8: howto manager. (line 2283) +* BFD_RELOC_M68HC11_PAGE: howto manager. (line 2307) +* BFD_RELOC_M68HC11_RL_GROUP: howto manager. (line 2296) +* BFD_RELOC_M68HC11_RL_JUMP: howto manager. (line 2290) +* BFD_RELOC_M68HC12_10_PCREL: howto manager. (line 2372) +* BFD_RELOC_M68HC12_16B: howto manager. (line 2366) +* BFD_RELOC_M68HC12_5B: howto manager. (line 2318) +* BFD_RELOC_M68HC12_9_PCREL: howto manager. (line 2369) +* BFD_RELOC_M68HC12_9B: howto manager. (line 2363) +* BFD_RELOC_M68HC12_HI8XG: howto manager. (line 2379) +* BFD_RELOC_M68HC12_LO8XG: howto manager. (line 2375) +* BFD_RELOC_MACH_O_LOCAL_SECTDIFF: howto manager. (line 2801) +* BFD_RELOC_MACH_O_PAIR: howto manager. (line 2804) +* BFD_RELOC_MACH_O_SECTDIFF: howto manager. (line 2797) +* BFD_RELOC_MACH_O_X86_64_BRANCH32: howto manager. (line 2807) +* BFD_RELOC_MACH_O_X86_64_BRANCH8: howto manager. (line 2808) +* BFD_RELOC_MACH_O_X86_64_GOT: howto manager. (line 2812) +* BFD_RELOC_MACH_O_X86_64_GOT_LOAD: howto manager. (line 2815) +* BFD_RELOC_MACH_O_X86_64_PCREL32_1: howto manager. (line 2825) +* BFD_RELOC_MACH_O_X86_64_PCREL32_2: howto manager. (line 2828) +* BFD_RELOC_MACH_O_X86_64_PCREL32_4: howto manager. (line 2831) +* BFD_RELOC_MACH_O_X86_64_SUBTRACTOR32: howto manager. (line 2819) +* BFD_RELOC_MACH_O_X86_64_SUBTRACTOR64: howto manager. (line 2822) +* BFD_RELOC_MCORE_PCREL_32: howto manager. (line 1696) +* BFD_RELOC_MCORE_PCREL_IMM11BY2: howto manager. (line 1694) +* BFD_RELOC_MCORE_PCREL_IMM4BY2: howto manager. (line 1695) +* BFD_RELOC_MCORE_PCREL_IMM8BY4: howto manager. (line 1693) +* BFD_RELOC_MCORE_PCREL_JSR_IMM11BY2: howto manager. (line 1697) +* BFD_RELOC_MCORE_RVA: howto manager. (line 1698) +* BFD_RELOC_MEP_16: howto manager. (line 1702) +* BFD_RELOC_MEP_32: howto manager. (line 1703) +* BFD_RELOC_MEP_8: howto manager. (line 1701) +* BFD_RELOC_MEP_ADDR24A4: howto manager. (line 1718) +* BFD_RELOC_MEP_GNU_VTENTRY: howto manager. (line 1720) +* BFD_RELOC_MEP_GNU_VTINHERIT: howto manager. (line 1719) +* BFD_RELOC_MEP_GPREL: howto manager. (line 1712) +* BFD_RELOC_MEP_HI16S: howto manager. (line 1711) +* BFD_RELOC_MEP_HI16U: howto manager. (line 1710) +* BFD_RELOC_MEP_LOW16: howto manager. (line 1709) +* BFD_RELOC_MEP_PCABS24A2: howto manager. (line 1708) +* BFD_RELOC_MEP_PCREL12A2: howto manager. (line 1705) +* BFD_RELOC_MEP_PCREL17A2: howto manager. (line 1706) +* BFD_RELOC_MEP_PCREL24A2: howto manager. (line 1707) +* BFD_RELOC_MEP_PCREL8A2: howto manager. (line 1704) +* BFD_RELOC_MEP_TPREL: howto manager. (line 1713) +* BFD_RELOC_MEP_TPREL7: howto manager. (line 1714) +* BFD_RELOC_MEP_TPREL7A2: howto manager. (line 1715) +* BFD_RELOC_MEP_TPREL7A4: howto manager. (line 1716) +* BFD_RELOC_MEP_UIMM24: howto manager. (line 1717) +* BFD_RELOC_METAG_COPY: howto manager. (line 1742) +* BFD_RELOC_METAG_GETSET_GOT: howto manager. (line 1734) +* BFD_RELOC_METAG_GETSET_GOTOFF: howto manager. (line 1733) +* BFD_RELOC_METAG_GETSETOFF: howto manager. (line 1726) +* BFD_RELOC_METAG_GLOB_DAT: howto manager. (line 1745) +* BFD_RELOC_METAG_GOTOFF: howto manager. (line 1740) +* BFD_RELOC_METAG_HI16_GOTOFF: howto manager. (line 1731) +* BFD_RELOC_METAG_HI16_GOTPC: howto manager. (line 1735) +* BFD_RELOC_METAG_HI16_PLT: howto manager. (line 1737) +* BFD_RELOC_METAG_HIADDR16: howto manager. (line 1723) +* BFD_RELOC_METAG_HIOG: howto manager. (line 1727) +* BFD_RELOC_METAG_JMP_SLOT: howto manager. (line 1743) +* BFD_RELOC_METAG_LO16_GOTOFF: howto manager. (line 1732) +* BFD_RELOC_METAG_LO16_GOTPC: howto manager. (line 1736) +* BFD_RELOC_METAG_LO16_PLT: howto manager. (line 1738) +* BFD_RELOC_METAG_LOADDR16: howto manager. (line 1724) +* BFD_RELOC_METAG_LOOG: howto manager. (line 1728) +* BFD_RELOC_METAG_PLT: howto manager. (line 1741) +* BFD_RELOC_METAG_REL16: howto manager. (line 1730) +* BFD_RELOC_METAG_REL8: howto manager. (line 1729) +* BFD_RELOC_METAG_RELATIVE: howto manager. (line 1744) +* BFD_RELOC_METAG_RELBRANCH: howto manager. (line 1725) +* BFD_RELOC_METAG_RELBRANCH_PLT: howto manager. (line 1739) +* BFD_RELOC_METAG_TLS_DTPMOD: howto manager. (line 1756) +* BFD_RELOC_METAG_TLS_DTPOFF: howto manager. (line 1757) +* BFD_RELOC_METAG_TLS_GD: howto manager. (line 1746) +* BFD_RELOC_METAG_TLS_IE: howto manager. (line 1751) +* BFD_RELOC_METAG_TLS_IENONPIC: howto manager. (line 1752) +* BFD_RELOC_METAG_TLS_IENONPIC_HI16: howto manager. (line 1753) +* BFD_RELOC_METAG_TLS_IENONPIC_LO16: howto manager. (line 1754) +* BFD_RELOC_METAG_TLS_LDM: howto manager. (line 1747) +* BFD_RELOC_METAG_TLS_LDO: howto manager. (line 1750) +* BFD_RELOC_METAG_TLS_LDO_HI16: howto manager. (line 1748) +* BFD_RELOC_METAG_TLS_LDO_LO16: howto manager. (line 1749) +* BFD_RELOC_METAG_TLS_LE: howto manager. (line 1758) +* BFD_RELOC_METAG_TLS_LE_HI16: howto manager. (line 1759) +* BFD_RELOC_METAG_TLS_LE_LO16: howto manager. (line 1760) +* BFD_RELOC_METAG_TLS_TPOFF: howto manager. (line 1755) +* BFD_RELOC_MICROBLAZE_32_GOTOFF: howto manager. (line 2878) +* BFD_RELOC_MICROBLAZE_32_LO: howto manager. (line 2834) +* BFD_RELOC_MICROBLAZE_32_LO_PCREL: howto manager. (line 2838) +* BFD_RELOC_MICROBLAZE_32_ROSDA: howto manager. (line 2842) +* BFD_RELOC_MICROBLAZE_32_RWSDA: howto manager. (line 2846) +* BFD_RELOC_MICROBLAZE_32_SYM_OP_SYM: howto manager. (line 2850) +* BFD_RELOC_MICROBLAZE_32_TLSDTPMOD: howto manager. (line 2899) +* BFD_RELOC_MICROBLAZE_32_TLSDTPREL: howto manager. (line 2902) +* BFD_RELOC_MICROBLAZE_64_GOT: howto manager. (line 2864) +* BFD_RELOC_MICROBLAZE_64_GOTOFF: howto manager. (line 2873) +* BFD_RELOC_MICROBLAZE_64_GOTPC: howto manager. (line 2859) +* BFD_RELOC_MICROBLAZE_64_NONE: howto manager. (line 2854) +* BFD_RELOC_MICROBLAZE_64_PLT: howto manager. (line 2868) +* BFD_RELOC_MICROBLAZE_64_TLS: howto manager. (line 2886) +* BFD_RELOC_MICROBLAZE_64_TLSDTPREL: howto manager. (line 2905) +* BFD_RELOC_MICROBLAZE_64_TLSGD: howto manager. (line 2889) +* BFD_RELOC_MICROBLAZE_64_TLSGOTTPREL: howto manager. (line 2909) +* BFD_RELOC_MICROBLAZE_64_TLSLD: howto manager. (line 2894) +* BFD_RELOC_MICROBLAZE_64_TLSTPREL: howto manager. (line 2913) +* BFD_RELOC_MICROBLAZE_COPY: howto manager. (line 2882) * BFD_RELOC_MICROMIPS_10_PCREL_S1: howto manager. (line 404) * BFD_RELOC_MICROMIPS_16_PCREL_S1: howto manager. (line 405) * BFD_RELOC_MICROMIPS_7_PCREL_S1: howto manager. (line 403) @@ -12059,8 +12439,9 @@ BFD Index * BFD_RELOC_MIPS_CALL16: howto manager. (line 416) * BFD_RELOC_MIPS_CALL_HI16: howto manager. (line 422) * BFD_RELOC_MIPS_CALL_LO16: howto manager. (line 424) -* BFD_RELOC_MIPS_COPY: howto manager. (line 471) +* BFD_RELOC_MIPS_COPY: howto manager. (line 472) * BFD_RELOC_MIPS_DELETE: howto manager. (line 438) +* BFD_RELOC_MIPS_EH: howto manager. (line 469) * BFD_RELOC_MIPS_GOT16: howto manager. (line 414) * BFD_RELOC_MIPS_GOT_DISP: howto manager. (line 432) * BFD_RELOC_MIPS_GOT_HI16: howto manager. (line 418) @@ -12073,7 +12454,7 @@ BFD Index * BFD_RELOC_MIPS_INSERT_B: howto manager. (line 437) * BFD_RELOC_MIPS_JALR: howto manager. (line 447) * BFD_RELOC_MIPS_JMP: howto manager. (line 342) -* BFD_RELOC_MIPS_JUMP_SLOT: howto manager. (line 472) +* BFD_RELOC_MIPS_JUMP_SLOT: howto manager. (line 473) * BFD_RELOC_MIPS_LITERAL: howto manager. (line 399) * BFD_RELOC_MIPS_REL16: howto manager. (line 445) * BFD_RELOC_MIPS_RELGOT: howto manager. (line 446) @@ -12094,406 +12475,521 @@ BFD Index * BFD_RELOC_MIPS_TLS_TPREL64: howto manager. (line 464) * BFD_RELOC_MIPS_TLS_TPREL_HI16: howto manager. (line 465) * BFD_RELOC_MIPS_TLS_TPREL_LO16: howto manager. (line 467) -* BFD_RELOC_MMIX_ADDR19: howto manager. (line 1607) -* BFD_RELOC_MMIX_ADDR27: howto manager. (line 1611) -* BFD_RELOC_MMIX_BASE_PLUS_OFFSET: howto manager. (line 1623) -* BFD_RELOC_MMIX_CBRANCH: howto manager. (line 1587) -* BFD_RELOC_MMIX_CBRANCH_1: howto manager. (line 1589) -* BFD_RELOC_MMIX_CBRANCH_2: howto manager. (line 1590) -* BFD_RELOC_MMIX_CBRANCH_3: howto manager. (line 1591) -* BFD_RELOC_MMIX_CBRANCH_J: howto manager. (line 1588) -* BFD_RELOC_MMIX_GETA: howto manager. (line 1581) -* BFD_RELOC_MMIX_GETA_1: howto manager. (line 1582) -* BFD_RELOC_MMIX_GETA_2: howto manager. (line 1583) -* BFD_RELOC_MMIX_GETA_3: howto manager. (line 1584) -* BFD_RELOC_MMIX_JMP: howto manager. (line 1601) -* BFD_RELOC_MMIX_JMP_1: howto manager. (line 1602) -* BFD_RELOC_MMIX_JMP_2: howto manager. (line 1603) -* BFD_RELOC_MMIX_JMP_3: howto manager. (line 1604) -* BFD_RELOC_MMIX_LOCAL: howto manager. (line 1627) -* BFD_RELOC_MMIX_PUSHJ: howto manager. (line 1594) -* BFD_RELOC_MMIX_PUSHJ_1: howto manager. (line 1595) -* BFD_RELOC_MMIX_PUSHJ_2: howto manager. (line 1596) -* BFD_RELOC_MMIX_PUSHJ_3: howto manager. (line 1597) -* BFD_RELOC_MMIX_PUSHJ_STUBBABLE: howto manager. (line 1598) -* BFD_RELOC_MMIX_REG: howto manager. (line 1619) -* BFD_RELOC_MMIX_REG_OR_BYTE: howto manager. (line 1615) -* BFD_RELOC_MN10300_16_PCREL: howto manager. (line 570) -* BFD_RELOC_MN10300_32_PCREL: howto manager. (line 566) -* BFD_RELOC_MN10300_ALIGN: howto manager. (line 551) -* BFD_RELOC_MN10300_COPY: howto manager. (line 534) -* BFD_RELOC_MN10300_GLOB_DAT: howto manager. (line 537) -* BFD_RELOC_MN10300_GOT16: howto manager. (line 530) -* BFD_RELOC_MN10300_GOT24: howto manager. (line 526) -* BFD_RELOC_MN10300_GOT32: howto manager. (line 522) -* BFD_RELOC_MN10300_GOTOFF24: howto manager. (line 519) -* BFD_RELOC_MN10300_JMP_SLOT: howto manager. (line 540) -* BFD_RELOC_MN10300_RELATIVE: howto manager. (line 543) -* BFD_RELOC_MN10300_SYM_DIFF: howto manager. (line 546) -* BFD_RELOC_MN10300_TLS_DTPMOD: howto manager. (line 561) -* BFD_RELOC_MN10300_TLS_DTPOFF: howto manager. (line 562) -* BFD_RELOC_MN10300_TLS_GD: howto manager. (line 555) -* BFD_RELOC_MN10300_TLS_GOTIE: howto manager. (line 558) -* BFD_RELOC_MN10300_TLS_IE: howto manager. (line 559) -* BFD_RELOC_MN10300_TLS_LD: howto manager. (line 556) -* BFD_RELOC_MN10300_TLS_LDO: howto manager. (line 557) -* BFD_RELOC_MN10300_TLS_LE: howto manager. (line 560) -* BFD_RELOC_MN10300_TLS_TPOFF: howto manager. (line 563) -* BFD_RELOC_MOXIE_10_PCREL: howto manager. (line 475) -* BFD_RELOC_MSP430_10_PCREL: howto manager. (line 2427) -* BFD_RELOC_MSP430_16: howto manager. (line 2429) -* BFD_RELOC_MSP430_16_BYTE: howto manager. (line 2431) -* BFD_RELOC_MSP430_16_PCREL: howto manager. (line 2428) -* BFD_RELOC_MSP430_16_PCREL_BYTE: howto manager. (line 2430) -* BFD_RELOC_MSP430_2X_PCREL: howto manager. (line 2432) -* BFD_RELOC_MSP430_RL_PCREL: howto manager. (line 2433) -* BFD_RELOC_MT_GNU_VTENTRY: howto manager. (line 2421) -* BFD_RELOC_MT_GNU_VTINHERIT: howto manager. (line 2418) -* BFD_RELOC_MT_HI16: howto manager. (line 2412) -* BFD_RELOC_MT_LO16: howto manager. (line 2415) -* BFD_RELOC_MT_PC16: howto manager. (line 2409) -* BFD_RELOC_MT_PCINSN8: howto manager. (line 2424) -* BFD_RELOC_NIOS2_ALIGN: howto manager. (line 2450) -* BFD_RELOC_NIOS2_CACHE_OPX: howto manager. (line 2440) -* BFD_RELOC_NIOS2_CALL16: howto manager. (line 2452) -* BFD_RELOC_NIOS2_CALL26: howto manager. (line 2438) -* BFD_RELOC_NIOS2_CALLR: howto manager. (line 2449) -* BFD_RELOC_NIOS2_CJMP: howto manager. (line 2448) -* BFD_RELOC_NIOS2_COPY: howto manager. (line 2465) -* BFD_RELOC_NIOS2_GLOB_DAT: howto manager. (line 2466) -* BFD_RELOC_NIOS2_GOT16: howto manager. (line 2451) -* BFD_RELOC_NIOS2_GOTOFF: howto manager. (line 2469) -* BFD_RELOC_NIOS2_GOTOFF_HA: howto manager. (line 2454) -* BFD_RELOC_NIOS2_GOTOFF_LO: howto manager. (line 2453) -* BFD_RELOC_NIOS2_GPREL: howto manager. (line 2446) -* BFD_RELOC_NIOS2_HI16: howto manager. (line 2443) -* BFD_RELOC_NIOS2_HIADJ16: howto manager. (line 2445) -* BFD_RELOC_NIOS2_IMM5: howto manager. (line 2439) -* BFD_RELOC_NIOS2_IMM6: howto manager. (line 2441) -* BFD_RELOC_NIOS2_IMM8: howto manager. (line 2442) -* BFD_RELOC_NIOS2_JUMP_SLOT: howto manager. (line 2467) -* BFD_RELOC_NIOS2_LO16: howto manager. (line 2444) -* BFD_RELOC_NIOS2_PCREL_HA: howto manager. (line 2456) -* BFD_RELOC_NIOS2_PCREL_LO: howto manager. (line 2455) -* BFD_RELOC_NIOS2_RELATIVE: howto manager. (line 2468) -* BFD_RELOC_NIOS2_S16: howto manager. (line 2436) -* BFD_RELOC_NIOS2_TLS_DTPMOD: howto manager. (line 2462) -* BFD_RELOC_NIOS2_TLS_DTPREL: howto manager. (line 2463) -* BFD_RELOC_NIOS2_TLS_GD16: howto manager. (line 2457) -* BFD_RELOC_NIOS2_TLS_IE16: howto manager. (line 2460) -* BFD_RELOC_NIOS2_TLS_LDM16: howto manager. (line 2458) -* BFD_RELOC_NIOS2_TLS_LDO16: howto manager. (line 2459) -* BFD_RELOC_NIOS2_TLS_LE16: howto manager. (line 2461) -* BFD_RELOC_NIOS2_TLS_TPREL: howto manager. (line 2464) -* BFD_RELOC_NIOS2_U16: howto manager. (line 2437) -* BFD_RELOC_NIOS2_UJMP: howto manager. (line 2447) +* BFD_RELOC_MMIX_ADDR19: howto manager. (line 1789) +* BFD_RELOC_MMIX_ADDR27: howto manager. (line 1793) +* BFD_RELOC_MMIX_BASE_PLUS_OFFSET: howto manager. (line 1805) +* BFD_RELOC_MMIX_CBRANCH: howto manager. (line 1769) +* BFD_RELOC_MMIX_CBRANCH_1: howto manager. (line 1771) +* BFD_RELOC_MMIX_CBRANCH_2: howto manager. (line 1772) +* BFD_RELOC_MMIX_CBRANCH_3: howto manager. (line 1773) +* BFD_RELOC_MMIX_CBRANCH_J: howto manager. (line 1770) +* BFD_RELOC_MMIX_GETA: howto manager. (line 1763) +* BFD_RELOC_MMIX_GETA_1: howto manager. (line 1764) +* BFD_RELOC_MMIX_GETA_2: howto manager. (line 1765) +* BFD_RELOC_MMIX_GETA_3: howto manager. (line 1766) +* BFD_RELOC_MMIX_JMP: howto manager. (line 1783) +* BFD_RELOC_MMIX_JMP_1: howto manager. (line 1784) +* BFD_RELOC_MMIX_JMP_2: howto manager. (line 1785) +* BFD_RELOC_MMIX_JMP_3: howto manager. (line 1786) +* BFD_RELOC_MMIX_LOCAL: howto manager. (line 1809) +* BFD_RELOC_MMIX_PUSHJ: howto manager. (line 1776) +* BFD_RELOC_MMIX_PUSHJ_1: howto manager. (line 1777) +* BFD_RELOC_MMIX_PUSHJ_2: howto manager. (line 1778) +* BFD_RELOC_MMIX_PUSHJ_3: howto manager. (line 1779) +* BFD_RELOC_MMIX_PUSHJ_STUBBABLE: howto manager. (line 1780) +* BFD_RELOC_MMIX_REG: howto manager. (line 1801) +* BFD_RELOC_MMIX_REG_OR_BYTE: howto manager. (line 1797) +* BFD_RELOC_MN10300_16_PCREL: howto manager. (line 571) +* BFD_RELOC_MN10300_32_PCREL: howto manager. (line 567) +* BFD_RELOC_MN10300_ALIGN: howto manager. (line 552) +* BFD_RELOC_MN10300_COPY: howto manager. (line 535) +* BFD_RELOC_MN10300_GLOB_DAT: howto manager. (line 538) +* BFD_RELOC_MN10300_GOT16: howto manager. (line 531) +* BFD_RELOC_MN10300_GOT24: howto manager. (line 527) +* BFD_RELOC_MN10300_GOT32: howto manager. (line 523) +* BFD_RELOC_MN10300_GOTOFF24: howto manager. (line 520) +* BFD_RELOC_MN10300_JMP_SLOT: howto manager. (line 541) +* BFD_RELOC_MN10300_RELATIVE: howto manager. (line 544) +* BFD_RELOC_MN10300_SYM_DIFF: howto manager. (line 547) +* BFD_RELOC_MN10300_TLS_DTPMOD: howto manager. (line 562) +* BFD_RELOC_MN10300_TLS_DTPOFF: howto manager. (line 563) +* BFD_RELOC_MN10300_TLS_GD: howto manager. (line 556) +* BFD_RELOC_MN10300_TLS_GOTIE: howto manager. (line 559) +* BFD_RELOC_MN10300_TLS_IE: howto manager. (line 560) +* BFD_RELOC_MN10300_TLS_LD: howto manager. (line 557) +* BFD_RELOC_MN10300_TLS_LDO: howto manager. (line 558) +* BFD_RELOC_MN10300_TLS_LE: howto manager. (line 561) +* BFD_RELOC_MN10300_TLS_TPOFF: howto manager. (line 564) +* BFD_RELOC_MOXIE_10_PCREL: howto manager. (line 476) +* BFD_RELOC_MSP430_10_PCREL: howto manager. (line 2621) +* BFD_RELOC_MSP430_16: howto manager. (line 2623) +* BFD_RELOC_MSP430_16_BYTE: howto manager. (line 2625) +* BFD_RELOC_MSP430_16_PCREL: howto manager. (line 2622) +* BFD_RELOC_MSP430_16_PCREL_BYTE: howto manager. (line 2624) +* BFD_RELOC_MSP430_2X_PCREL: howto manager. (line 2626) +* BFD_RELOC_MSP430_ABS8: howto manager. (line 2628) +* BFD_RELOC_MSP430_ABS_HI16: howto manager. (line 2640) +* BFD_RELOC_MSP430_PREL31: howto manager. (line 2641) +* BFD_RELOC_MSP430_RL_PCREL: howto manager. (line 2627) +* BFD_RELOC_MSP430_SYM_DIFF: howto manager. (line 2642) +* BFD_RELOC_MSP430X_ABS16: howto manager. (line 2639) +* BFD_RELOC_MSP430X_ABS20_ADR_DST: howto manager. (line 2636) +* BFD_RELOC_MSP430X_ABS20_ADR_SRC: howto manager. (line 2635) +* BFD_RELOC_MSP430X_ABS20_EXT_DST: howto manager. (line 2633) +* BFD_RELOC_MSP430X_ABS20_EXT_ODST: howto manager. (line 2634) +* BFD_RELOC_MSP430X_ABS20_EXT_SRC: howto manager. (line 2632) +* BFD_RELOC_MSP430X_PCR16: howto manager. (line 2637) +* BFD_RELOC_MSP430X_PCR20_CALL: howto manager. (line 2638) +* BFD_RELOC_MSP430X_PCR20_EXT_DST: howto manager. (line 2630) +* BFD_RELOC_MSP430X_PCR20_EXT_ODST: howto manager. (line 2631) +* BFD_RELOC_MSP430X_PCR20_EXT_SRC: howto manager. (line 2629) +* BFD_RELOC_MT_GNU_VTENTRY: howto manager. (line 2615) +* BFD_RELOC_MT_GNU_VTINHERIT: howto manager. (line 2612) +* BFD_RELOC_MT_HI16: howto manager. (line 2606) +* BFD_RELOC_MT_LO16: howto manager. (line 2609) +* BFD_RELOC_MT_PC16: howto manager. (line 2603) +* BFD_RELOC_MT_PCINSN8: howto manager. (line 2618) +* BFD_RELOC_NDS32_10_UPCREL: howto manager. (line 1438) +* BFD_RELOC_NDS32_10IFCU_PCREL: howto manager. (line 1466) +* BFD_RELOC_NDS32_15_FIXED: howto manager. (line 1399) +* BFD_RELOC_NDS32_15_PCREL: howto manager. (line 1307) +* BFD_RELOC_NDS32_17_FIXED: howto manager. (line 1400) +* BFD_RELOC_NDS32_17_PCREL: howto manager. (line 1310) +* BFD_RELOC_NDS32_17IFC_PCREL: howto manager. (line 1465) +* BFD_RELOC_NDS32_20: howto manager. (line 1296) +* BFD_RELOC_NDS32_25_ABS: howto manager. (line 1462) +* BFD_RELOC_NDS32_25_FIXED: howto manager. (line 1401) +* BFD_RELOC_NDS32_25_PCREL: howto manager. (line 1313) +* BFD_RELOC_NDS32_25_PLTREL: howto manager. (line 1374) +* BFD_RELOC_NDS32_5: howto manager. (line 1435) +* BFD_RELOC_NDS32_9_FIXED: howto manager. (line 1398) +* BFD_RELOC_NDS32_9_PCREL: howto manager. (line 1299) +* BFD_RELOC_NDS32_9_PLTREL: howto manager. (line 1373) +* BFD_RELOC_NDS32_COPY: howto manager. (line 1375) +* BFD_RELOC_NDS32_DATA: howto manager. (line 1463) +* BFD_RELOC_NDS32_DIFF16: howto manager. (line 1459) +* BFD_RELOC_NDS32_DIFF32: howto manager. (line 1460) +* BFD_RELOC_NDS32_DIFF8: howto manager. (line 1458) +* BFD_RELOC_NDS32_DIFF_ULEB128: howto manager. (line 1461) +* BFD_RELOC_NDS32_DWARF2_LEB: howto manager. (line 1418) +* BFD_RELOC_NDS32_DWARF2_OP1: howto manager. (line 1416) +* BFD_RELOC_NDS32_DWARF2_OP2: howto manager. (line 1417) +* BFD_RELOC_NDS32_GLOB_DAT: howto manager. (line 1376) +* BFD_RELOC_NDS32_GOT15S2: howto manager. (line 1431) +* BFD_RELOC_NDS32_GOT17S2: howto manager. (line 1432) +* BFD_RELOC_NDS32_GOT20: howto manager. (line 1372) +* BFD_RELOC_NDS32_GOT_HI20: howto manager. (line 1383) +* BFD_RELOC_NDS32_GOT_LO12: howto manager. (line 1384) +* BFD_RELOC_NDS32_GOT_LO15: howto manager. (line 1427) +* BFD_RELOC_NDS32_GOT_LO19: howto manager. (line 1428) +* BFD_RELOC_NDS32_GOT_SUFF: howto manager. (line 1446) +* BFD_RELOC_NDS32_GOTOFF: howto manager. (line 1379) +* BFD_RELOC_NDS32_GOTOFF_HI20: howto manager. (line 1380) +* BFD_RELOC_NDS32_GOTOFF_LO12: howto manager. (line 1381) +* BFD_RELOC_NDS32_GOTOFF_LO15: howto manager. (line 1429) +* BFD_RELOC_NDS32_GOTOFF_LO19: howto manager. (line 1430) +* BFD_RELOC_NDS32_GOTOFF_SUFF: howto manager. (line 1447) +* BFD_RELOC_NDS32_GOTPC20: howto manager. (line 1382) +* BFD_RELOC_NDS32_GOTPC_HI20: howto manager. (line 1385) +* BFD_RELOC_NDS32_GOTPC_LO12: howto manager. (line 1386) +* BFD_RELOC_NDS32_HI20: howto manager. (line 1316) +* BFD_RELOC_NDS32_INSN16: howto manager. (line 1389) +* BFD_RELOC_NDS32_JMP_SLOT: howto manager. (line 1377) +* BFD_RELOC_NDS32_LABEL: howto manager. (line 1390) +* BFD_RELOC_NDS32_LO12S0: howto manager. (line 1332) +* BFD_RELOC_NDS32_LO12S0_ORI: howto manager. (line 1336) +* BFD_RELOC_NDS32_LO12S1: howto manager. (line 1328) +* BFD_RELOC_NDS32_LO12S2: howto manager. (line 1324) +* BFD_RELOC_NDS32_LO12S2_DP: howto manager. (line 1412) +* BFD_RELOC_NDS32_LO12S2_SP: howto manager. (line 1413) +* BFD_RELOC_NDS32_LO12S3: howto manager. (line 1320) +* BFD_RELOC_NDS32_LOADSTORE: howto manager. (line 1397) +* BFD_RELOC_NDS32_LONGCALL1: howto manager. (line 1391) +* BFD_RELOC_NDS32_LONGCALL2: howto manager. (line 1392) +* BFD_RELOC_NDS32_LONGCALL3: howto manager. (line 1393) +* BFD_RELOC_NDS32_LONGJUMP1: howto manager. (line 1394) +* BFD_RELOC_NDS32_LONGJUMP2: howto manager. (line 1395) +* BFD_RELOC_NDS32_LONGJUMP3: howto manager. (line 1396) +* BFD_RELOC_NDS32_MINUEND: howto manager. (line 1456) +* BFD_RELOC_NDS32_MULCALL_SUFF: howto manager. (line 1449) +* BFD_RELOC_NDS32_PLT_GOT_SUFF: howto manager. (line 1448) +* BFD_RELOC_NDS32_PLT_GOTREL_HI20: howto manager. (line 1406) +* BFD_RELOC_NDS32_PLT_GOTREL_LO12: howto manager. (line 1407) +* BFD_RELOC_NDS32_PLT_GOTREL_LO15: howto manager. (line 1425) +* BFD_RELOC_NDS32_PLT_GOTREL_LO19: howto manager. (line 1426) +* BFD_RELOC_NDS32_PLT_GOTREL_LO20: howto manager. (line 1424) +* BFD_RELOC_NDS32_PLTBLOCK: howto manager. (line 1453) +* BFD_RELOC_NDS32_PLTREL_HI20: howto manager. (line 1404) +* BFD_RELOC_NDS32_PLTREL_LO12: howto manager. (line 1405) +* BFD_RELOC_NDS32_PTR: howto manager. (line 1450) +* BFD_RELOC_NDS32_PTR_COUNT: howto manager. (line 1451) +* BFD_RELOC_NDS32_PTR_RESOLVED: howto manager. (line 1452) +* BFD_RELOC_NDS32_RELATIVE: howto manager. (line 1378) +* BFD_RELOC_NDS32_RELAX_ENTRY: howto manager. (line 1445) +* BFD_RELOC_NDS32_RELAX_REGION_BEGIN: howto manager. (line 1454) +* BFD_RELOC_NDS32_RELAX_REGION_END: howto manager. (line 1455) +* BFD_RELOC_NDS32_SDA12S2_DP: howto manager. (line 1410) +* BFD_RELOC_NDS32_SDA12S2_SP: howto manager. (line 1411) +* BFD_RELOC_NDS32_SDA15S0: howto manager. (line 1352) +* BFD_RELOC_NDS32_SDA15S1: howto manager. (line 1348) +* BFD_RELOC_NDS32_SDA15S2: howto manager. (line 1344) +* BFD_RELOC_NDS32_SDA15S3: howto manager. (line 1340) +* BFD_RELOC_NDS32_SDA16S3: howto manager. (line 1356) +* BFD_RELOC_NDS32_SDA17S2: howto manager. (line 1360) +* BFD_RELOC_NDS32_SDA18S1: howto manager. (line 1364) +* BFD_RELOC_NDS32_SDA19S0: howto manager. (line 1368) +* BFD_RELOC_NDS32_SDA_FP7U2_RELA: howto manager. (line 1442) +* BFD_RELOC_NDS32_SUBTRAHEND: howto manager. (line 1457) +* BFD_RELOC_NDS32_TRAN: howto manager. (line 1464) +* BFD_RELOC_NDS32_UPDATE_TA: howto manager. (line 1421) +* BFD_RELOC_NDS32_WORD_9_PCREL: howto manager. (line 1303) +* BFD_RELOC_NIOS2_ALIGN: howto manager. (line 2659) +* BFD_RELOC_NIOS2_CACHE_OPX: howto manager. (line 2649) +* BFD_RELOC_NIOS2_CALL16: howto manager. (line 2661) +* BFD_RELOC_NIOS2_CALL26: howto manager. (line 2647) +* BFD_RELOC_NIOS2_CALLR: howto manager. (line 2658) +* BFD_RELOC_NIOS2_CJMP: howto manager. (line 2657) +* BFD_RELOC_NIOS2_COPY: howto manager. (line 2674) +* BFD_RELOC_NIOS2_GLOB_DAT: howto manager. (line 2675) +* BFD_RELOC_NIOS2_GOT16: howto manager. (line 2660) +* BFD_RELOC_NIOS2_GOTOFF: howto manager. (line 2678) +* BFD_RELOC_NIOS2_GOTOFF_HA: howto manager. (line 2663) +* BFD_RELOC_NIOS2_GOTOFF_LO: howto manager. (line 2662) +* BFD_RELOC_NIOS2_GPREL: howto manager. (line 2655) +* BFD_RELOC_NIOS2_HI16: howto manager. (line 2652) +* BFD_RELOC_NIOS2_HIADJ16: howto manager. (line 2654) +* BFD_RELOC_NIOS2_IMM5: howto manager. (line 2648) +* BFD_RELOC_NIOS2_IMM6: howto manager. (line 2650) +* BFD_RELOC_NIOS2_IMM8: howto manager. (line 2651) +* BFD_RELOC_NIOS2_JUMP_SLOT: howto manager. (line 2676) +* BFD_RELOC_NIOS2_LO16: howto manager. (line 2653) +* BFD_RELOC_NIOS2_PCREL_HA: howto manager. (line 2665) +* BFD_RELOC_NIOS2_PCREL_LO: howto manager. (line 2664) +* BFD_RELOC_NIOS2_RELATIVE: howto manager. (line 2677) +* BFD_RELOC_NIOS2_S16: howto manager. (line 2645) +* BFD_RELOC_NIOS2_TLS_DTPMOD: howto manager. (line 2671) +* BFD_RELOC_NIOS2_TLS_DTPREL: howto manager. (line 2672) +* BFD_RELOC_NIOS2_TLS_GD16: howto manager. (line 2666) +* BFD_RELOC_NIOS2_TLS_IE16: howto manager. (line 2669) +* BFD_RELOC_NIOS2_TLS_LDM16: howto manager. (line 2667) +* BFD_RELOC_NIOS2_TLS_LDO16: howto manager. (line 2668) +* BFD_RELOC_NIOS2_TLS_LE16: howto manager. (line 2670) +* BFD_RELOC_NIOS2_TLS_TPREL: howto manager. (line 2673) +* BFD_RELOC_NIOS2_U16: howto manager. (line 2646) +* BFD_RELOC_NIOS2_UJMP: howto manager. (line 2656) * BFD_RELOC_NONE: howto manager. (line 135) -* BFD_RELOC_NS32K_DISP_16: howto manager. (line 636) -* BFD_RELOC_NS32K_DISP_16_PCREL: howto manager. (line 639) -* BFD_RELOC_NS32K_DISP_32: howto manager. (line 637) -* BFD_RELOC_NS32K_DISP_32_PCREL: howto manager. (line 640) -* BFD_RELOC_NS32K_DISP_8: howto manager. (line 635) -* BFD_RELOC_NS32K_DISP_8_PCREL: howto manager. (line 638) -* BFD_RELOC_NS32K_IMM_16: howto manager. (line 630) -* BFD_RELOC_NS32K_IMM_16_PCREL: howto manager. (line 633) -* BFD_RELOC_NS32K_IMM_32: howto manager. (line 631) -* BFD_RELOC_NS32K_IMM_32_PCREL: howto manager. (line 634) -* BFD_RELOC_NS32K_IMM_8: howto manager. (line 629) -* BFD_RELOC_NS32K_IMM_8_PCREL: howto manager. (line 632) -* BFD_RELOC_OPENRISC_ABS_26: howto manager. (line 2377) -* BFD_RELOC_OPENRISC_REL_26: howto manager. (line 2378) -* BFD_RELOC_PDP11_DISP_6_PCREL: howto manager. (line 644) -* BFD_RELOC_PDP11_DISP_8_PCREL: howto manager. (line 643) -* BFD_RELOC_PJ_CODE_DIR16: howto manager. (line 649) -* BFD_RELOC_PJ_CODE_DIR32: howto manager. (line 650) -* BFD_RELOC_PJ_CODE_HI16: howto manager. (line 647) -* BFD_RELOC_PJ_CODE_LO16: howto manager. (line 648) -* BFD_RELOC_PJ_CODE_REL16: howto manager. (line 651) -* BFD_RELOC_PJ_CODE_REL32: howto manager. (line 652) -* BFD_RELOC_PPC64_ADDR16_DS: howto manager. (line 714) -* BFD_RELOC_PPC64_ADDR16_LO_DS: howto manager. (line 715) -* BFD_RELOC_PPC64_DTPREL16_DS: howto manager. (line 763) -* BFD_RELOC_PPC64_DTPREL16_HIGHER: howto manager. (line 765) -* BFD_RELOC_PPC64_DTPREL16_HIGHERA: howto manager. (line 766) -* BFD_RELOC_PPC64_DTPREL16_HIGHEST: howto manager. (line 767) -* BFD_RELOC_PPC64_DTPREL16_HIGHESTA: howto manager. (line 768) -* BFD_RELOC_PPC64_DTPREL16_LO_DS: howto manager. (line 764) -* BFD_RELOC_PPC64_GOT16_DS: howto manager. (line 716) -* BFD_RELOC_PPC64_GOT16_LO_DS: howto manager. (line 717) -* BFD_RELOC_PPC64_HIGHER: howto manager. (line 702) -* BFD_RELOC_PPC64_HIGHER_S: howto manager. (line 703) -* BFD_RELOC_PPC64_HIGHEST: howto manager. (line 704) -* BFD_RELOC_PPC64_HIGHEST_S: howto manager. (line 705) -* BFD_RELOC_PPC64_PLT16_LO_DS: howto manager. (line 718) -* BFD_RELOC_PPC64_PLTGOT16: howto manager. (line 710) -* BFD_RELOC_PPC64_PLTGOT16_DS: howto manager. (line 723) -* BFD_RELOC_PPC64_PLTGOT16_HA: howto manager. (line 713) -* BFD_RELOC_PPC64_PLTGOT16_HI: howto manager. (line 712) -* BFD_RELOC_PPC64_PLTGOT16_LO: howto manager. (line 711) -* BFD_RELOC_PPC64_PLTGOT16_LO_DS: howto manager. (line 724) -* BFD_RELOC_PPC64_SECTOFF_DS: howto manager. (line 719) -* BFD_RELOC_PPC64_SECTOFF_LO_DS: howto manager. (line 720) -* BFD_RELOC_PPC64_TOC: howto manager. (line 709) -* BFD_RELOC_PPC64_TOC16_DS: howto manager. (line 721) -* BFD_RELOC_PPC64_TOC16_HA: howto manager. (line 708) -* BFD_RELOC_PPC64_TOC16_HI: howto manager. (line 707) -* BFD_RELOC_PPC64_TOC16_LO: howto manager. (line 706) -* BFD_RELOC_PPC64_TOC16_LO_DS: howto manager. (line 722) -* BFD_RELOC_PPC64_TPREL16_DS: howto manager. (line 757) -* BFD_RELOC_PPC64_TPREL16_HIGHER: howto manager. (line 759) -* BFD_RELOC_PPC64_TPREL16_HIGHERA: howto manager. (line 760) -* BFD_RELOC_PPC64_TPREL16_HIGHEST: howto manager. (line 761) -* BFD_RELOC_PPC64_TPREL16_HIGHESTA: howto manager. (line 762) -* BFD_RELOC_PPC64_TPREL16_LO_DS: howto manager. (line 758) -* BFD_RELOC_PPC_B16: howto manager. (line 658) -* BFD_RELOC_PPC_B16_BRNTAKEN: howto manager. (line 660) -* BFD_RELOC_PPC_B16_BRTAKEN: howto manager. (line 659) -* BFD_RELOC_PPC_B26: howto manager. (line 655) -* BFD_RELOC_PPC_BA16: howto manager. (line 661) -* BFD_RELOC_PPC_BA16_BRNTAKEN: howto manager. (line 663) -* BFD_RELOC_PPC_BA16_BRTAKEN: howto manager. (line 662) -* BFD_RELOC_PPC_BA26: howto manager. (line 656) -* BFD_RELOC_PPC_COPY: howto manager. (line 664) -* BFD_RELOC_PPC_DTPMOD: howto manager. (line 730) -* BFD_RELOC_PPC_DTPREL: howto manager. (line 740) -* BFD_RELOC_PPC_DTPREL16: howto manager. (line 736) -* BFD_RELOC_PPC_DTPREL16_HA: howto manager. (line 739) -* BFD_RELOC_PPC_DTPREL16_HI: howto manager. (line 738) -* BFD_RELOC_PPC_DTPREL16_LO: howto manager. (line 737) -* BFD_RELOC_PPC_EMB_BIT_FLD: howto manager. (line 683) -* BFD_RELOC_PPC_EMB_MRKREF: howto manager. (line 678) -* BFD_RELOC_PPC_EMB_NADDR16: howto manager. (line 670) -* BFD_RELOC_PPC_EMB_NADDR16_HA: howto manager. (line 673) -* BFD_RELOC_PPC_EMB_NADDR16_HI: howto manager. (line 672) -* BFD_RELOC_PPC_EMB_NADDR16_LO: howto manager. (line 671) -* BFD_RELOC_PPC_EMB_NADDR32: howto manager. (line 669) -* BFD_RELOC_PPC_EMB_RELSDA: howto manager. (line 684) -* BFD_RELOC_PPC_EMB_RELSEC16: howto manager. (line 679) -* BFD_RELOC_PPC_EMB_RELST_HA: howto manager. (line 682) -* BFD_RELOC_PPC_EMB_RELST_HI: howto manager. (line 681) -* BFD_RELOC_PPC_EMB_RELST_LO: howto manager. (line 680) -* BFD_RELOC_PPC_EMB_SDA21: howto manager. (line 677) -* BFD_RELOC_PPC_EMB_SDA2I16: howto manager. (line 675) -* BFD_RELOC_PPC_EMB_SDA2REL: howto manager. (line 676) -* BFD_RELOC_PPC_EMB_SDAI16: howto manager. (line 674) -* BFD_RELOC_PPC_GLOB_DAT: howto manager. (line 665) -* BFD_RELOC_PPC_GOT_DTPREL16: howto manager. (line 753) -* BFD_RELOC_PPC_GOT_DTPREL16_HA: howto manager. (line 756) -* BFD_RELOC_PPC_GOT_DTPREL16_HI: howto manager. (line 755) -* BFD_RELOC_PPC_GOT_DTPREL16_LO: howto manager. (line 754) -* BFD_RELOC_PPC_GOT_TLSGD16: howto manager. (line 741) -* BFD_RELOC_PPC_GOT_TLSGD16_HA: howto manager. (line 744) -* BFD_RELOC_PPC_GOT_TLSGD16_HI: howto manager. (line 743) -* BFD_RELOC_PPC_GOT_TLSGD16_LO: howto manager. (line 742) -* BFD_RELOC_PPC_GOT_TLSLD16: howto manager. (line 745) -* BFD_RELOC_PPC_GOT_TLSLD16_HA: howto manager. (line 748) -* BFD_RELOC_PPC_GOT_TLSLD16_HI: howto manager. (line 747) -* BFD_RELOC_PPC_GOT_TLSLD16_LO: howto manager. (line 746) -* BFD_RELOC_PPC_GOT_TPREL16: howto manager. (line 749) -* BFD_RELOC_PPC_GOT_TPREL16_HA: howto manager. (line 752) -* BFD_RELOC_PPC_GOT_TPREL16_HI: howto manager. (line 751) -* BFD_RELOC_PPC_GOT_TPREL16_LO: howto manager. (line 750) -* BFD_RELOC_PPC_JMP_SLOT: howto manager. (line 666) -* BFD_RELOC_PPC_LOCAL24PC: howto manager. (line 668) -* BFD_RELOC_PPC_RELATIVE: howto manager. (line 667) -* BFD_RELOC_PPC_TLS: howto manager. (line 727) -* BFD_RELOC_PPC_TLSGD: howto manager. (line 728) -* BFD_RELOC_PPC_TLSLD: howto manager. (line 729) -* BFD_RELOC_PPC_TOC16: howto manager. (line 657) -* BFD_RELOC_PPC_TPREL: howto manager. (line 735) -* BFD_RELOC_PPC_TPREL16: howto manager. (line 731) -* BFD_RELOC_PPC_TPREL16_HA: howto manager. (line 734) -* BFD_RELOC_PPC_TPREL16_HI: howto manager. (line 733) -* BFD_RELOC_PPC_TPREL16_LO: howto manager. (line 732) -* BFD_RELOC_PPC_VLE_HA16A: howto manager. (line 692) -* BFD_RELOC_PPC_VLE_HA16D: howto manager. (line 693) -* BFD_RELOC_PPC_VLE_HI16A: howto manager. (line 690) -* BFD_RELOC_PPC_VLE_HI16D: howto manager. (line 691) -* BFD_RELOC_PPC_VLE_LO16A: howto manager. (line 688) -* BFD_RELOC_PPC_VLE_LO16D: howto manager. (line 689) -* BFD_RELOC_PPC_VLE_REL15: howto manager. (line 686) -* BFD_RELOC_PPC_VLE_REL24: howto manager. (line 687) -* BFD_RELOC_PPC_VLE_REL8: howto manager. (line 685) -* BFD_RELOC_PPC_VLE_SDA21: howto manager. (line 694) -* BFD_RELOC_PPC_VLE_SDA21_LO: howto manager. (line 695) -* BFD_RELOC_PPC_VLE_SDAREL_HA16A: howto manager. (line 700) -* BFD_RELOC_PPC_VLE_SDAREL_HA16D: howto manager. (line 701) -* BFD_RELOC_PPC_VLE_SDAREL_HI16A: howto manager. (line 698) -* BFD_RELOC_PPC_VLE_SDAREL_HI16D: howto manager. (line 699) -* BFD_RELOC_PPC_VLE_SDAREL_LO16A: howto manager. (line 696) -* BFD_RELOC_PPC_VLE_SDAREL_LO16D: howto manager. (line 697) -* BFD_RELOC_RELC: howto manager. (line 2395) -* BFD_RELOC_RL78_16_OP: howto manager. (line 1750) -* BFD_RELOC_RL78_16U: howto manager. (line 1754) -* BFD_RELOC_RL78_24_OP: howto manager. (line 1751) -* BFD_RELOC_RL78_24U: howto manager. (line 1755) -* BFD_RELOC_RL78_32_OP: howto manager. (line 1752) -* BFD_RELOC_RL78_8U: howto manager. (line 1753) -* BFD_RELOC_RL78_ABS16: howto manager. (line 1767) -* BFD_RELOC_RL78_ABS16_REV: howto manager. (line 1768) -* BFD_RELOC_RL78_ABS16U: howto manager. (line 1771) -* BFD_RELOC_RL78_ABS16UL: howto manager. (line 1773) -* BFD_RELOC_RL78_ABS16UW: howto manager. (line 1772) -* BFD_RELOC_RL78_ABS32: howto manager. (line 1769) -* BFD_RELOC_RL78_ABS32_REV: howto manager. (line 1770) -* BFD_RELOC_RL78_ABS8: howto manager. (line 1766) -* BFD_RELOC_RL78_CODE: howto manager. (line 1778) -* BFD_RELOC_RL78_DIFF: howto manager. (line 1757) -* BFD_RELOC_RL78_DIR3U_PCREL: howto manager. (line 1756) -* BFD_RELOC_RL78_GPRELB: howto manager. (line 1758) -* BFD_RELOC_RL78_GPRELL: howto manager. (line 1760) -* BFD_RELOC_RL78_GPRELW: howto manager. (line 1759) -* BFD_RELOC_RL78_HI16: howto manager. (line 1775) -* BFD_RELOC_RL78_HI8: howto manager. (line 1776) -* BFD_RELOC_RL78_LO16: howto manager. (line 1777) -* BFD_RELOC_RL78_NEG16: howto manager. (line 1747) -* BFD_RELOC_RL78_NEG24: howto manager. (line 1748) -* BFD_RELOC_RL78_NEG32: howto manager. (line 1749) -* BFD_RELOC_RL78_NEG8: howto manager. (line 1746) -* BFD_RELOC_RL78_OP_AND: howto manager. (line 1764) -* BFD_RELOC_RL78_OP_NEG: howto manager. (line 1763) -* BFD_RELOC_RL78_OP_SHRA: howto manager. (line 1765) -* BFD_RELOC_RL78_OP_SUBTRACT: howto manager. (line 1762) -* BFD_RELOC_RL78_RELAX: howto manager. (line 1774) -* BFD_RELOC_RL78_SYM: howto manager. (line 1761) +* BFD_RELOC_NS32K_DISP_16: howto manager. (line 639) +* BFD_RELOC_NS32K_DISP_16_PCREL: howto manager. (line 642) +* BFD_RELOC_NS32K_DISP_32: howto manager. (line 640) +* BFD_RELOC_NS32K_DISP_32_PCREL: howto manager. (line 643) +* BFD_RELOC_NS32K_DISP_8: howto manager. (line 638) +* BFD_RELOC_NS32K_DISP_8_PCREL: howto manager. (line 641) +* BFD_RELOC_NS32K_IMM_16: howto manager. (line 633) +* BFD_RELOC_NS32K_IMM_16_PCREL: howto manager. (line 636) +* BFD_RELOC_NS32K_IMM_32: howto manager. (line 634) +* BFD_RELOC_NS32K_IMM_32_PCREL: howto manager. (line 637) +* BFD_RELOC_NS32K_IMM_8: howto manager. (line 632) +* BFD_RELOC_NS32K_IMM_8_PCREL: howto manager. (line 635) +* BFD_RELOC_OPENRISC_ABS_26: howto manager. (line 2571) +* BFD_RELOC_OPENRISC_REL_26: howto manager. (line 2572) +* BFD_RELOC_PDP11_DISP_6_PCREL: howto manager. (line 647) +* BFD_RELOC_PDP11_DISP_8_PCREL: howto manager. (line 646) +* BFD_RELOC_PJ_CODE_DIR16: howto manager. (line 652) +* BFD_RELOC_PJ_CODE_DIR32: howto manager. (line 653) +* BFD_RELOC_PJ_CODE_HI16: howto manager. (line 650) +* BFD_RELOC_PJ_CODE_LO16: howto manager. (line 651) +* BFD_RELOC_PJ_CODE_REL16: howto manager. (line 654) +* BFD_RELOC_PJ_CODE_REL32: howto manager. (line 655) +* BFD_RELOC_PPC64_ADDR16_DS: howto manager. (line 717) +* BFD_RELOC_PPC64_ADDR16_HIGH: howto manager. (line 728) +* BFD_RELOC_PPC64_ADDR16_HIGHA: howto manager. (line 729) +* BFD_RELOC_PPC64_ADDR16_LO_DS: howto manager. (line 718) +* BFD_RELOC_PPC64_DTPREL16_DS: howto manager. (line 768) +* BFD_RELOC_PPC64_DTPREL16_HIGH: howto manager. (line 776) +* BFD_RELOC_PPC64_DTPREL16_HIGHA: howto manager. (line 777) +* BFD_RELOC_PPC64_DTPREL16_HIGHER: howto manager. (line 770) +* BFD_RELOC_PPC64_DTPREL16_HIGHERA: howto manager. (line 771) +* BFD_RELOC_PPC64_DTPREL16_HIGHEST: howto manager. (line 772) +* BFD_RELOC_PPC64_DTPREL16_HIGHESTA: howto manager. (line 773) +* BFD_RELOC_PPC64_DTPREL16_LO_DS: howto manager. (line 769) +* BFD_RELOC_PPC64_GOT16_DS: howto manager. (line 719) +* BFD_RELOC_PPC64_GOT16_LO_DS: howto manager. (line 720) +* BFD_RELOC_PPC64_HIGHER: howto manager. (line 705) +* BFD_RELOC_PPC64_HIGHER_S: howto manager. (line 706) +* BFD_RELOC_PPC64_HIGHEST: howto manager. (line 707) +* BFD_RELOC_PPC64_HIGHEST_S: howto manager. (line 708) +* BFD_RELOC_PPC64_PLT16_LO_DS: howto manager. (line 721) +* BFD_RELOC_PPC64_PLTGOT16: howto manager. (line 713) +* BFD_RELOC_PPC64_PLTGOT16_DS: howto manager. (line 726) +* BFD_RELOC_PPC64_PLTGOT16_HA: howto manager. (line 716) +* BFD_RELOC_PPC64_PLTGOT16_HI: howto manager. (line 715) +* BFD_RELOC_PPC64_PLTGOT16_LO: howto manager. (line 714) +* BFD_RELOC_PPC64_PLTGOT16_LO_DS: howto manager. (line 727) +* BFD_RELOC_PPC64_SECTOFF_DS: howto manager. (line 722) +* BFD_RELOC_PPC64_SECTOFF_LO_DS: howto manager. (line 723) +* BFD_RELOC_PPC64_TOC: howto manager. (line 712) +* BFD_RELOC_PPC64_TOC16_DS: howto manager. (line 724) +* BFD_RELOC_PPC64_TOC16_HA: howto manager. (line 711) +* BFD_RELOC_PPC64_TOC16_HI: howto manager. (line 710) +* BFD_RELOC_PPC64_TOC16_LO: howto manager. (line 709) +* BFD_RELOC_PPC64_TOC16_LO_DS: howto manager. (line 725) +* BFD_RELOC_PPC64_TPREL16_DS: howto manager. (line 762) +* BFD_RELOC_PPC64_TPREL16_HIGH: howto manager. (line 774) +* BFD_RELOC_PPC64_TPREL16_HIGHA: howto manager. (line 775) +* BFD_RELOC_PPC64_TPREL16_HIGHER: howto manager. (line 764) +* BFD_RELOC_PPC64_TPREL16_HIGHERA: howto manager. (line 765) +* BFD_RELOC_PPC64_TPREL16_HIGHEST: howto manager. (line 766) +* BFD_RELOC_PPC64_TPREL16_HIGHESTA: howto manager. (line 767) +* BFD_RELOC_PPC64_TPREL16_LO_DS: howto manager. (line 763) +* BFD_RELOC_PPC_B16: howto manager. (line 661) +* BFD_RELOC_PPC_B16_BRNTAKEN: howto manager. (line 663) +* BFD_RELOC_PPC_B16_BRTAKEN: howto manager. (line 662) +* BFD_RELOC_PPC_B26: howto manager. (line 658) +* BFD_RELOC_PPC_BA16: howto manager. (line 664) +* BFD_RELOC_PPC_BA16_BRNTAKEN: howto manager. (line 666) +* BFD_RELOC_PPC_BA16_BRTAKEN: howto manager. (line 665) +* BFD_RELOC_PPC_BA26: howto manager. (line 659) +* BFD_RELOC_PPC_COPY: howto manager. (line 667) +* BFD_RELOC_PPC_DTPMOD: howto manager. (line 735) +* BFD_RELOC_PPC_DTPREL: howto manager. (line 745) +* BFD_RELOC_PPC_DTPREL16: howto manager. (line 741) +* BFD_RELOC_PPC_DTPREL16_HA: howto manager. (line 744) +* BFD_RELOC_PPC_DTPREL16_HI: howto manager. (line 743) +* BFD_RELOC_PPC_DTPREL16_LO: howto manager. (line 742) +* BFD_RELOC_PPC_EMB_BIT_FLD: howto manager. (line 686) +* BFD_RELOC_PPC_EMB_MRKREF: howto manager. (line 681) +* BFD_RELOC_PPC_EMB_NADDR16: howto manager. (line 673) +* BFD_RELOC_PPC_EMB_NADDR16_HA: howto manager. (line 676) +* BFD_RELOC_PPC_EMB_NADDR16_HI: howto manager. (line 675) +* BFD_RELOC_PPC_EMB_NADDR16_LO: howto manager. (line 674) +* BFD_RELOC_PPC_EMB_NADDR32: howto manager. (line 672) +* BFD_RELOC_PPC_EMB_RELSDA: howto manager. (line 687) +* BFD_RELOC_PPC_EMB_RELSEC16: howto manager. (line 682) +* BFD_RELOC_PPC_EMB_RELST_HA: howto manager. (line 685) +* BFD_RELOC_PPC_EMB_RELST_HI: howto manager. (line 684) +* BFD_RELOC_PPC_EMB_RELST_LO: howto manager. (line 683) +* BFD_RELOC_PPC_EMB_SDA21: howto manager. (line 680) +* BFD_RELOC_PPC_EMB_SDA2I16: howto manager. (line 678) +* BFD_RELOC_PPC_EMB_SDA2REL: howto manager. (line 679) +* BFD_RELOC_PPC_EMB_SDAI16: howto manager. (line 677) +* BFD_RELOC_PPC_GLOB_DAT: howto manager. (line 668) +* BFD_RELOC_PPC_GOT_DTPREL16: howto manager. (line 758) +* BFD_RELOC_PPC_GOT_DTPREL16_HA: howto manager. (line 761) +* BFD_RELOC_PPC_GOT_DTPREL16_HI: howto manager. (line 760) +* BFD_RELOC_PPC_GOT_DTPREL16_LO: howto manager. (line 759) +* BFD_RELOC_PPC_GOT_TLSGD16: howto manager. (line 746) +* BFD_RELOC_PPC_GOT_TLSGD16_HA: howto manager. (line 749) +* BFD_RELOC_PPC_GOT_TLSGD16_HI: howto manager. (line 748) +* BFD_RELOC_PPC_GOT_TLSGD16_LO: howto manager. (line 747) +* BFD_RELOC_PPC_GOT_TLSLD16: howto manager. (line 750) +* BFD_RELOC_PPC_GOT_TLSLD16_HA: howto manager. (line 753) +* BFD_RELOC_PPC_GOT_TLSLD16_HI: howto manager. (line 752) +* BFD_RELOC_PPC_GOT_TLSLD16_LO: howto manager. (line 751) +* BFD_RELOC_PPC_GOT_TPREL16: howto manager. (line 754) +* BFD_RELOC_PPC_GOT_TPREL16_HA: howto manager. (line 757) +* BFD_RELOC_PPC_GOT_TPREL16_HI: howto manager. (line 756) +* BFD_RELOC_PPC_GOT_TPREL16_LO: howto manager. (line 755) +* BFD_RELOC_PPC_JMP_SLOT: howto manager. (line 669) +* BFD_RELOC_PPC_LOCAL24PC: howto manager. (line 671) +* BFD_RELOC_PPC_RELATIVE: howto manager. (line 670) +* BFD_RELOC_PPC_TLS: howto manager. (line 732) +* BFD_RELOC_PPC_TLSGD: howto manager. (line 733) +* BFD_RELOC_PPC_TLSLD: howto manager. (line 734) +* BFD_RELOC_PPC_TOC16: howto manager. (line 660) +* BFD_RELOC_PPC_TPREL: howto manager. (line 740) +* BFD_RELOC_PPC_TPREL16: howto manager. (line 736) +* BFD_RELOC_PPC_TPREL16_HA: howto manager. (line 739) +* BFD_RELOC_PPC_TPREL16_HI: howto manager. (line 738) +* BFD_RELOC_PPC_TPREL16_LO: howto manager. (line 737) +* BFD_RELOC_PPC_VLE_HA16A: howto manager. (line 695) +* BFD_RELOC_PPC_VLE_HA16D: howto manager. (line 696) +* BFD_RELOC_PPC_VLE_HI16A: howto manager. (line 693) +* BFD_RELOC_PPC_VLE_HI16D: howto manager. (line 694) +* BFD_RELOC_PPC_VLE_LO16A: howto manager. (line 691) +* BFD_RELOC_PPC_VLE_LO16D: howto manager. (line 692) +* BFD_RELOC_PPC_VLE_REL15: howto manager. (line 689) +* BFD_RELOC_PPC_VLE_REL24: howto manager. (line 690) +* BFD_RELOC_PPC_VLE_REL8: howto manager. (line 688) +* BFD_RELOC_PPC_VLE_SDA21: howto manager. (line 697) +* BFD_RELOC_PPC_VLE_SDA21_LO: howto manager. (line 698) +* BFD_RELOC_PPC_VLE_SDAREL_HA16A: howto manager. (line 703) +* BFD_RELOC_PPC_VLE_SDAREL_HA16D: howto manager. (line 704) +* BFD_RELOC_PPC_VLE_SDAREL_HI16A: howto manager. (line 701) +* BFD_RELOC_PPC_VLE_SDAREL_HI16D: howto manager. (line 702) +* BFD_RELOC_PPC_VLE_SDAREL_LO16A: howto manager. (line 699) +* BFD_RELOC_PPC_VLE_SDAREL_LO16D: howto manager. (line 700) +* BFD_RELOC_RELC: howto manager. (line 2589) +* BFD_RELOC_RL78_16_OP: howto manager. (line 1932) +* BFD_RELOC_RL78_16U: howto manager. (line 1936) +* BFD_RELOC_RL78_24_OP: howto manager. (line 1933) +* BFD_RELOC_RL78_24U: howto manager. (line 1937) +* BFD_RELOC_RL78_32_OP: howto manager. (line 1934) +* BFD_RELOC_RL78_8U: howto manager. (line 1935) +* BFD_RELOC_RL78_ABS16: howto manager. (line 1949) +* BFD_RELOC_RL78_ABS16_REV: howto manager. (line 1950) +* BFD_RELOC_RL78_ABS16U: howto manager. (line 1953) +* BFD_RELOC_RL78_ABS16UL: howto manager. (line 1955) +* BFD_RELOC_RL78_ABS16UW: howto manager. (line 1954) +* BFD_RELOC_RL78_ABS32: howto manager. (line 1951) +* BFD_RELOC_RL78_ABS32_REV: howto manager. (line 1952) +* BFD_RELOC_RL78_ABS8: howto manager. (line 1948) +* BFD_RELOC_RL78_CODE: howto manager. (line 1960) +* BFD_RELOC_RL78_DIFF: howto manager. (line 1939) +* BFD_RELOC_RL78_DIR3U_PCREL: howto manager. (line 1938) +* BFD_RELOC_RL78_GPRELB: howto manager. (line 1940) +* BFD_RELOC_RL78_GPRELL: howto manager. (line 1942) +* BFD_RELOC_RL78_GPRELW: howto manager. (line 1941) +* BFD_RELOC_RL78_HI16: howto manager. (line 1957) +* BFD_RELOC_RL78_HI8: howto manager. (line 1958) +* BFD_RELOC_RL78_LO16: howto manager. (line 1959) +* BFD_RELOC_RL78_NEG16: howto manager. (line 1929) +* BFD_RELOC_RL78_NEG24: howto manager. (line 1930) +* BFD_RELOC_RL78_NEG32: howto manager. (line 1931) +* BFD_RELOC_RL78_NEG8: howto manager. (line 1928) +* BFD_RELOC_RL78_OP_AND: howto manager. (line 1946) +* BFD_RELOC_RL78_OP_NEG: howto manager. (line 1945) +* BFD_RELOC_RL78_OP_SHRA: howto manager. (line 1947) +* BFD_RELOC_RL78_OP_SUBTRACT: howto manager. (line 1944) +* BFD_RELOC_RL78_RELAX: howto manager. (line 1956) +* BFD_RELOC_RL78_SYM: howto manager. (line 1943) * BFD_RELOC_RVA: howto manager. (line 104) -* BFD_RELOC_RX_16_OP: howto manager. (line 1785) -* BFD_RELOC_RX_16U: howto manager. (line 1789) -* BFD_RELOC_RX_24_OP: howto manager. (line 1786) -* BFD_RELOC_RX_24U: howto manager. (line 1790) -* BFD_RELOC_RX_32_OP: howto manager. (line 1787) -* BFD_RELOC_RX_8U: howto manager. (line 1788) -* BFD_RELOC_RX_ABS16: howto manager. (line 1800) -* BFD_RELOC_RX_ABS16_REV: howto manager. (line 1801) -* BFD_RELOC_RX_ABS16U: howto manager. (line 1804) -* BFD_RELOC_RX_ABS16UL: howto manager. (line 1806) -* BFD_RELOC_RX_ABS16UW: howto manager. (line 1805) -* BFD_RELOC_RX_ABS32: howto manager. (line 1802) -* BFD_RELOC_RX_ABS32_REV: howto manager. (line 1803) -* BFD_RELOC_RX_ABS8: howto manager. (line 1799) -* BFD_RELOC_RX_DIFF: howto manager. (line 1792) -* BFD_RELOC_RX_DIR3U_PCREL: howto manager. (line 1791) -* BFD_RELOC_RX_GPRELB: howto manager. (line 1793) -* BFD_RELOC_RX_GPRELL: howto manager. (line 1795) -* BFD_RELOC_RX_GPRELW: howto manager. (line 1794) -* BFD_RELOC_RX_NEG16: howto manager. (line 1782) -* BFD_RELOC_RX_NEG24: howto manager. (line 1783) -* BFD_RELOC_RX_NEG32: howto manager. (line 1784) -* BFD_RELOC_RX_NEG8: howto manager. (line 1781) -* BFD_RELOC_RX_OP_NEG: howto manager. (line 1798) -* BFD_RELOC_RX_OP_SUBTRACT: howto manager. (line 1797) -* BFD_RELOC_RX_RELAX: howto manager. (line 1807) -* BFD_RELOC_RX_SYM: howto manager. (line 1796) -* BFD_RELOC_SCORE16_BRANCH: howto manager. (line 1938) -* BFD_RELOC_SCORE16_JMP: howto manager. (line 1935) -* BFD_RELOC_SCORE_BCMP: howto manager. (line 1941) -* BFD_RELOC_SCORE_BRANCH: howto manager. (line 1926) -* BFD_RELOC_SCORE_CALL15: howto manager. (line 1946) -* BFD_RELOC_SCORE_DUMMY2: howto manager. (line 1922) -* BFD_RELOC_SCORE_DUMMY_HI16: howto manager. (line 1947) -* BFD_RELOC_SCORE_GOT15: howto manager. (line 1944) -* BFD_RELOC_SCORE_GOT_LO16: howto manager. (line 1945) -* BFD_RELOC_SCORE_GPREL15: howto manager. (line 1919) -* BFD_RELOC_SCORE_IMM30: howto manager. (line 1929) -* BFD_RELOC_SCORE_IMM32: howto manager. (line 1932) -* BFD_RELOC_SCORE_JMP: howto manager. (line 1923) -* BFD_RELOC_SH_ALIGN: howto manager. (line 962) -* BFD_RELOC_SH_CODE: howto manager. (line 963) -* BFD_RELOC_SH_COPY: howto manager. (line 968) -* BFD_RELOC_SH_COPY64: howto manager. (line 993) -* BFD_RELOC_SH_COUNT: howto manager. (line 961) -* BFD_RELOC_SH_DATA: howto manager. (line 964) -* BFD_RELOC_SH_DISP12: howto manager. (line 944) -* BFD_RELOC_SH_DISP12BY2: howto manager. (line 945) -* BFD_RELOC_SH_DISP12BY4: howto manager. (line 946) -* BFD_RELOC_SH_DISP12BY8: howto manager. (line 947) -* BFD_RELOC_SH_DISP20: howto manager. (line 948) -* BFD_RELOC_SH_DISP20BY8: howto manager. (line 949) -* BFD_RELOC_SH_FUNCDESC: howto manager. (line 1036) -* BFD_RELOC_SH_GLOB_DAT: howto manager. (line 969) -* BFD_RELOC_SH_GLOB_DAT64: howto manager. (line 994) -* BFD_RELOC_SH_GOT10BY4: howto manager. (line 997) -* BFD_RELOC_SH_GOT10BY8: howto manager. (line 998) -* BFD_RELOC_SH_GOT20: howto manager. (line 1030) -* BFD_RELOC_SH_GOT_HI16: howto manager. (line 976) -* BFD_RELOC_SH_GOT_LOW16: howto manager. (line 973) -* BFD_RELOC_SH_GOT_MEDHI16: howto manager. (line 975) -* BFD_RELOC_SH_GOT_MEDLOW16: howto manager. (line 974) -* BFD_RELOC_SH_GOTFUNCDESC: howto manager. (line 1032) -* BFD_RELOC_SH_GOTFUNCDESC20: howto manager. (line 1033) -* BFD_RELOC_SH_GOTOFF20: howto manager. (line 1031) -* BFD_RELOC_SH_GOTOFF_HI16: howto manager. (line 988) -* BFD_RELOC_SH_GOTOFF_LOW16: howto manager. (line 985) -* BFD_RELOC_SH_GOTOFF_MEDHI16: howto manager. (line 987) -* BFD_RELOC_SH_GOTOFF_MEDLOW16: howto manager. (line 986) -* BFD_RELOC_SH_GOTOFFFUNCDESC: howto manager. (line 1034) -* BFD_RELOC_SH_GOTOFFFUNCDESC20: howto manager. (line 1035) -* BFD_RELOC_SH_GOTPC: howto manager. (line 972) -* BFD_RELOC_SH_GOTPC_HI16: howto manager. (line 992) -* BFD_RELOC_SH_GOTPC_LOW16: howto manager. (line 989) -* BFD_RELOC_SH_GOTPC_MEDHI16: howto manager. (line 991) -* BFD_RELOC_SH_GOTPC_MEDLOW16: howto manager. (line 990) -* BFD_RELOC_SH_GOTPLT10BY4: howto manager. (line 999) -* BFD_RELOC_SH_GOTPLT10BY8: howto manager. (line 1000) -* BFD_RELOC_SH_GOTPLT32: howto manager. (line 1001) -* BFD_RELOC_SH_GOTPLT_HI16: howto manager. (line 980) -* BFD_RELOC_SH_GOTPLT_LOW16: howto manager. (line 977) -* BFD_RELOC_SH_GOTPLT_MEDHI16: howto manager. (line 979) -* BFD_RELOC_SH_GOTPLT_MEDLOW16: howto manager. (line 978) -* BFD_RELOC_SH_IMM3: howto manager. (line 942) -* BFD_RELOC_SH_IMM3U: howto manager. (line 943) -* BFD_RELOC_SH_IMM4: howto manager. (line 950) -* BFD_RELOC_SH_IMM4BY2: howto manager. (line 951) -* BFD_RELOC_SH_IMM4BY4: howto manager. (line 952) -* BFD_RELOC_SH_IMM8: howto manager. (line 953) -* BFD_RELOC_SH_IMM8BY2: howto manager. (line 954) -* BFD_RELOC_SH_IMM8BY4: howto manager. (line 955) -* BFD_RELOC_SH_IMM_HI16: howto manager. (line 1019) -* BFD_RELOC_SH_IMM_HI16_PCREL: howto manager. (line 1020) -* BFD_RELOC_SH_IMM_LOW16: howto manager. (line 1013) -* BFD_RELOC_SH_IMM_LOW16_PCREL: howto manager. (line 1014) -* BFD_RELOC_SH_IMM_MEDHI16: howto manager. (line 1017) -* BFD_RELOC_SH_IMM_MEDHI16_PCREL: howto manager. (line 1018) -* BFD_RELOC_SH_IMM_MEDLOW16: howto manager. (line 1015) -* BFD_RELOC_SH_IMM_MEDLOW16_PCREL: howto manager. (line 1016) -* BFD_RELOC_SH_IMMS10: howto manager. (line 1007) -* BFD_RELOC_SH_IMMS10BY2: howto manager. (line 1008) -* BFD_RELOC_SH_IMMS10BY4: howto manager. (line 1009) -* BFD_RELOC_SH_IMMS10BY8: howto manager. (line 1010) -* BFD_RELOC_SH_IMMS16: howto manager. (line 1011) -* BFD_RELOC_SH_IMMS6: howto manager. (line 1004) -* BFD_RELOC_SH_IMMS6BY32: howto manager. (line 1005) -* BFD_RELOC_SH_IMMU16: howto manager. (line 1012) -* BFD_RELOC_SH_IMMU5: howto manager. (line 1003) -* BFD_RELOC_SH_IMMU6: howto manager. (line 1006) -* BFD_RELOC_SH_JMP_SLOT: howto manager. (line 970) -* BFD_RELOC_SH_JMP_SLOT64: howto manager. (line 995) -* BFD_RELOC_SH_LABEL: howto manager. (line 965) -* BFD_RELOC_SH_LOOP_END: howto manager. (line 967) -* BFD_RELOC_SH_LOOP_START: howto manager. (line 966) -* BFD_RELOC_SH_PCDISP12BY2: howto manager. (line 941) -* BFD_RELOC_SH_PCDISP8BY2: howto manager. (line 940) -* BFD_RELOC_SH_PCRELIMM8BY2: howto manager. (line 956) -* BFD_RELOC_SH_PCRELIMM8BY4: howto manager. (line 957) -* BFD_RELOC_SH_PLT_HI16: howto manager. (line 984) -* BFD_RELOC_SH_PLT_LOW16: howto manager. (line 981) -* BFD_RELOC_SH_PLT_MEDHI16: howto manager. (line 983) -* BFD_RELOC_SH_PLT_MEDLOW16: howto manager. (line 982) -* BFD_RELOC_SH_PT_16: howto manager. (line 1021) -* BFD_RELOC_SH_RELATIVE: howto manager. (line 971) -* BFD_RELOC_SH_RELATIVE64: howto manager. (line 996) -* BFD_RELOC_SH_SHMEDIA_CODE: howto manager. (line 1002) -* BFD_RELOC_SH_SWITCH16: howto manager. (line 958) -* BFD_RELOC_SH_SWITCH32: howto manager. (line 959) -* BFD_RELOC_SH_TLS_DTPMOD32: howto manager. (line 1027) -* BFD_RELOC_SH_TLS_DTPOFF32: howto manager. (line 1028) -* BFD_RELOC_SH_TLS_GD_32: howto manager. (line 1022) -* BFD_RELOC_SH_TLS_IE_32: howto manager. (line 1025) -* BFD_RELOC_SH_TLS_LD_32: howto manager. (line 1023) -* BFD_RELOC_SH_TLS_LDO_32: howto manager. (line 1024) -* BFD_RELOC_SH_TLS_LE_32: howto manager. (line 1026) -* BFD_RELOC_SH_TLS_TPOFF32: howto manager. (line 1029) -* BFD_RELOC_SH_USES: howto manager. (line 960) +* BFD_RELOC_RX_16_OP: howto manager. (line 1967) +* BFD_RELOC_RX_16U: howto manager. (line 1971) +* BFD_RELOC_RX_24_OP: howto manager. (line 1968) +* BFD_RELOC_RX_24U: howto manager. (line 1972) +* BFD_RELOC_RX_32_OP: howto manager. (line 1969) +* BFD_RELOC_RX_8U: howto manager. (line 1970) +* BFD_RELOC_RX_ABS16: howto manager. (line 1982) +* BFD_RELOC_RX_ABS16_REV: howto manager. (line 1983) +* BFD_RELOC_RX_ABS16U: howto manager. (line 1986) +* BFD_RELOC_RX_ABS16UL: howto manager. (line 1988) +* BFD_RELOC_RX_ABS16UW: howto manager. (line 1987) +* BFD_RELOC_RX_ABS32: howto manager. (line 1984) +* BFD_RELOC_RX_ABS32_REV: howto manager. (line 1985) +* BFD_RELOC_RX_ABS8: howto manager. (line 1981) +* BFD_RELOC_RX_DIFF: howto manager. (line 1974) +* BFD_RELOC_RX_DIR3U_PCREL: howto manager. (line 1973) +* BFD_RELOC_RX_GPRELB: howto manager. (line 1975) +* BFD_RELOC_RX_GPRELL: howto manager. (line 1977) +* BFD_RELOC_RX_GPRELW: howto manager. (line 1976) +* BFD_RELOC_RX_NEG16: howto manager. (line 1964) +* BFD_RELOC_RX_NEG24: howto manager. (line 1965) +* BFD_RELOC_RX_NEG32: howto manager. (line 1966) +* BFD_RELOC_RX_NEG8: howto manager. (line 1963) +* BFD_RELOC_RX_OP_NEG: howto manager. (line 1980) +* BFD_RELOC_RX_OP_SUBTRACT: howto manager. (line 1979) +* BFD_RELOC_RX_RELAX: howto manager. (line 1989) +* BFD_RELOC_RX_SYM: howto manager. (line 1978) +* BFD_RELOC_SCORE16_BRANCH: howto manager. (line 2132) +* BFD_RELOC_SCORE16_JMP: howto manager. (line 2129) +* BFD_RELOC_SCORE_BCMP: howto manager. (line 2135) +* BFD_RELOC_SCORE_BRANCH: howto manager. (line 2120) +* BFD_RELOC_SCORE_CALL15: howto manager. (line 2140) +* BFD_RELOC_SCORE_DUMMY2: howto manager. (line 2116) +* BFD_RELOC_SCORE_DUMMY_HI16: howto manager. (line 2141) +* BFD_RELOC_SCORE_GOT15: howto manager. (line 2138) +* BFD_RELOC_SCORE_GOT_LO16: howto manager. (line 2139) +* BFD_RELOC_SCORE_GPREL15: howto manager. (line 2113) +* BFD_RELOC_SCORE_IMM30: howto manager. (line 2123) +* BFD_RELOC_SCORE_IMM32: howto manager. (line 2126) +* BFD_RELOC_SCORE_JMP: howto manager. (line 2117) +* BFD_RELOC_SH_ALIGN: howto manager. (line 971) +* BFD_RELOC_SH_CODE: howto manager. (line 972) +* BFD_RELOC_SH_COPY: howto manager. (line 977) +* BFD_RELOC_SH_COPY64: howto manager. (line 1002) +* BFD_RELOC_SH_COUNT: howto manager. (line 970) +* BFD_RELOC_SH_DATA: howto manager. (line 973) +* BFD_RELOC_SH_DISP12: howto manager. (line 953) +* BFD_RELOC_SH_DISP12BY2: howto manager. (line 954) +* BFD_RELOC_SH_DISP12BY4: howto manager. (line 955) +* BFD_RELOC_SH_DISP12BY8: howto manager. (line 956) +* BFD_RELOC_SH_DISP20: howto manager. (line 957) +* BFD_RELOC_SH_DISP20BY8: howto manager. (line 958) +* BFD_RELOC_SH_FUNCDESC: howto manager. (line 1045) +* BFD_RELOC_SH_GLOB_DAT: howto manager. (line 978) +* BFD_RELOC_SH_GLOB_DAT64: howto manager. (line 1003) +* BFD_RELOC_SH_GOT10BY4: howto manager. (line 1006) +* BFD_RELOC_SH_GOT10BY8: howto manager. (line 1007) +* BFD_RELOC_SH_GOT20: howto manager. (line 1039) +* BFD_RELOC_SH_GOT_HI16: howto manager. (line 985) +* BFD_RELOC_SH_GOT_LOW16: howto manager. (line 982) +* BFD_RELOC_SH_GOT_MEDHI16: howto manager. (line 984) +* BFD_RELOC_SH_GOT_MEDLOW16: howto manager. (line 983) +* BFD_RELOC_SH_GOTFUNCDESC: howto manager. (line 1041) +* BFD_RELOC_SH_GOTFUNCDESC20: howto manager. (line 1042) +* BFD_RELOC_SH_GOTOFF20: howto manager. (line 1040) +* BFD_RELOC_SH_GOTOFF_HI16: howto manager. (line 997) +* BFD_RELOC_SH_GOTOFF_LOW16: howto manager. (line 994) +* BFD_RELOC_SH_GOTOFF_MEDHI16: howto manager. (line 996) +* BFD_RELOC_SH_GOTOFF_MEDLOW16: howto manager. (line 995) +* BFD_RELOC_SH_GOTOFFFUNCDESC: howto manager. (line 1043) +* BFD_RELOC_SH_GOTOFFFUNCDESC20: howto manager. (line 1044) +* BFD_RELOC_SH_GOTPC: howto manager. (line 981) +* BFD_RELOC_SH_GOTPC_HI16: howto manager. (line 1001) +* BFD_RELOC_SH_GOTPC_LOW16: howto manager. (line 998) +* BFD_RELOC_SH_GOTPC_MEDHI16: howto manager. (line 1000) +* BFD_RELOC_SH_GOTPC_MEDLOW16: howto manager. (line 999) +* BFD_RELOC_SH_GOTPLT10BY4: howto manager. (line 1008) +* BFD_RELOC_SH_GOTPLT10BY8: howto manager. (line 1009) +* BFD_RELOC_SH_GOTPLT32: howto manager. (line 1010) +* BFD_RELOC_SH_GOTPLT_HI16: howto manager. (line 989) +* BFD_RELOC_SH_GOTPLT_LOW16: howto manager. (line 986) +* BFD_RELOC_SH_GOTPLT_MEDHI16: howto manager. (line 988) +* BFD_RELOC_SH_GOTPLT_MEDLOW16: howto manager. (line 987) +* BFD_RELOC_SH_IMM3: howto manager. (line 951) +* BFD_RELOC_SH_IMM3U: howto manager. (line 952) +* BFD_RELOC_SH_IMM4: howto manager. (line 959) +* BFD_RELOC_SH_IMM4BY2: howto manager. (line 960) +* BFD_RELOC_SH_IMM4BY4: howto manager. (line 961) +* BFD_RELOC_SH_IMM8: howto manager. (line 962) +* BFD_RELOC_SH_IMM8BY2: howto manager. (line 963) +* BFD_RELOC_SH_IMM8BY4: howto manager. (line 964) +* BFD_RELOC_SH_IMM_HI16: howto manager. (line 1028) +* BFD_RELOC_SH_IMM_HI16_PCREL: howto manager. (line 1029) +* BFD_RELOC_SH_IMM_LOW16: howto manager. (line 1022) +* BFD_RELOC_SH_IMM_LOW16_PCREL: howto manager. (line 1023) +* BFD_RELOC_SH_IMM_MEDHI16: howto manager. (line 1026) +* BFD_RELOC_SH_IMM_MEDHI16_PCREL: howto manager. (line 1027) +* BFD_RELOC_SH_IMM_MEDLOW16: howto manager. (line 1024) +* BFD_RELOC_SH_IMM_MEDLOW16_PCREL: howto manager. (line 1025) +* BFD_RELOC_SH_IMMS10: howto manager. (line 1016) +* BFD_RELOC_SH_IMMS10BY2: howto manager. (line 1017) +* BFD_RELOC_SH_IMMS10BY4: howto manager. (line 1018) +* BFD_RELOC_SH_IMMS10BY8: howto manager. (line 1019) +* BFD_RELOC_SH_IMMS16: howto manager. (line 1020) +* BFD_RELOC_SH_IMMS6: howto manager. (line 1013) +* BFD_RELOC_SH_IMMS6BY32: howto manager. (line 1014) +* BFD_RELOC_SH_IMMU16: howto manager. (line 1021) +* BFD_RELOC_SH_IMMU5: howto manager. (line 1012) +* BFD_RELOC_SH_IMMU6: howto manager. (line 1015) +* BFD_RELOC_SH_JMP_SLOT: howto manager. (line 979) +* BFD_RELOC_SH_JMP_SLOT64: howto manager. (line 1004) +* BFD_RELOC_SH_LABEL: howto manager. (line 974) +* BFD_RELOC_SH_LOOP_END: howto manager. (line 976) +* BFD_RELOC_SH_LOOP_START: howto manager. (line 975) +* BFD_RELOC_SH_PCDISP12BY2: howto manager. (line 950) +* BFD_RELOC_SH_PCDISP8BY2: howto manager. (line 949) +* BFD_RELOC_SH_PCRELIMM8BY2: howto manager. (line 965) +* BFD_RELOC_SH_PCRELIMM8BY4: howto manager. (line 966) +* BFD_RELOC_SH_PLT_HI16: howto manager. (line 993) +* BFD_RELOC_SH_PLT_LOW16: howto manager. (line 990) +* BFD_RELOC_SH_PLT_MEDHI16: howto manager. (line 992) +* BFD_RELOC_SH_PLT_MEDLOW16: howto manager. (line 991) +* BFD_RELOC_SH_PT_16: howto manager. (line 1030) +* BFD_RELOC_SH_RELATIVE: howto manager. (line 980) +* BFD_RELOC_SH_RELATIVE64: howto manager. (line 1005) +* BFD_RELOC_SH_SHMEDIA_CODE: howto manager. (line 1011) +* BFD_RELOC_SH_SWITCH16: howto manager. (line 967) +* BFD_RELOC_SH_SWITCH32: howto manager. (line 968) +* BFD_RELOC_SH_TLS_DTPMOD32: howto manager. (line 1036) +* BFD_RELOC_SH_TLS_DTPOFF32: howto manager. (line 1037) +* BFD_RELOC_SH_TLS_GD_32: howto manager. (line 1031) +* BFD_RELOC_SH_TLS_IE_32: howto manager. (line 1034) +* BFD_RELOC_SH_TLS_LD_32: howto manager. (line 1032) +* BFD_RELOC_SH_TLS_LDO_32: howto manager. (line 1033) +* BFD_RELOC_SH_TLS_LE_32: howto manager. (line 1035) +* BFD_RELOC_SH_TLS_TPOFF32: howto manager. (line 1038) +* BFD_RELOC_SH_USES: howto manager. (line 969) * BFD_RELOC_SIZE32: howto manager. (line 74) * BFD_RELOC_SIZE64: howto manager. (line 75) * BFD_RELOC_SPARC13: howto manager. (line 138) @@ -12589,373 +13085,375 @@ BFD Index * BFD_RELOC_SPU_PCREL9b: howto manager. (line 233) * BFD_RELOC_SPU_PPU32: howto manager. (line 237) * BFD_RELOC_SPU_PPU64: howto manager. (line 238) -* BFD_RELOC_THUMB_PCREL_BLX: howto manager. (line 789) -* BFD_RELOC_THUMB_PCREL_BRANCH12: howto manager. (line 803) -* BFD_RELOC_THUMB_PCREL_BRANCH20: howto manager. (line 804) -* BFD_RELOC_THUMB_PCREL_BRANCH23: howto manager. (line 805) -* BFD_RELOC_THUMB_PCREL_BRANCH25: howto manager. (line 806) -* BFD_RELOC_THUMB_PCREL_BRANCH7: howto manager. (line 801) -* BFD_RELOC_THUMB_PCREL_BRANCH9: howto manager. (line 802) -* BFD_RELOC_TIC30_LDP: howto manager. (line 1421) -* BFD_RELOC_TIC54X_16_OF_23: howto manager. (line 1439) -* BFD_RELOC_TIC54X_23: howto manager. (line 1436) -* BFD_RELOC_TIC54X_MS7_OF_23: howto manager. (line 1444) -* BFD_RELOC_TIC54X_PARTLS7: howto manager. (line 1426) -* BFD_RELOC_TIC54X_PARTMS9: howto manager. (line 1431) -* BFD_RELOC_TILEGX_BROFF_X1: howto manager. (line 3029) -* BFD_RELOC_TILEGX_COPY: howto manager. (line 3025) -* BFD_RELOC_TILEGX_DEST_IMM8_X1: howto manager. (line 3036) -* BFD_RELOC_TILEGX_GLOB_DAT: howto manager. (line 3026) -* BFD_RELOC_TILEGX_HW0: howto manager. (line 3018) -* BFD_RELOC_TILEGX_HW0_LAST: howto manager. (line 3022) -* BFD_RELOC_TILEGX_HW1: howto manager. (line 3019) -* BFD_RELOC_TILEGX_HW1_LAST: howto manager. (line 3023) -* BFD_RELOC_TILEGX_HW2: howto manager. (line 3020) -* BFD_RELOC_TILEGX_HW2_LAST: howto manager. (line 3024) -* BFD_RELOC_TILEGX_HW3: howto manager. (line 3021) -* BFD_RELOC_TILEGX_IMM16_X0_HW0: howto manager. (line 3045) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_GOT: howto manager. (line 3073) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST: howto manager. (line 3053) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_GOT: howto manager. (line 3081) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_PCREL: howto manager. (line 3067) +* BFD_RELOC_THUMB_PCREL_BLX: howto manager. (line 798) +* BFD_RELOC_THUMB_PCREL_BRANCH12: howto manager. (line 812) +* BFD_RELOC_THUMB_PCREL_BRANCH20: howto manager. (line 813) +* BFD_RELOC_THUMB_PCREL_BRANCH23: howto manager. (line 814) +* BFD_RELOC_THUMB_PCREL_BRANCH25: howto manager. (line 815) +* BFD_RELOC_THUMB_PCREL_BRANCH7: howto manager. (line 810) +* BFD_RELOC_THUMB_PCREL_BRANCH9: howto manager. (line 811) +* BFD_RELOC_TIC30_LDP: howto manager. (line 1603) +* BFD_RELOC_TIC54X_16_OF_23: howto manager. (line 1621) +* BFD_RELOC_TIC54X_23: howto manager. (line 1618) +* BFD_RELOC_TIC54X_MS7_OF_23: howto manager. (line 1626) +* BFD_RELOC_TIC54X_PARTLS7: howto manager. (line 1608) +* BFD_RELOC_TIC54X_PARTMS9: howto manager. (line 1613) +* BFD_RELOC_TILEGX_BROFF_X1: howto manager. (line 3305) +* BFD_RELOC_TILEGX_COPY: howto manager. (line 3301) +* BFD_RELOC_TILEGX_DEST_IMM8_X1: howto manager. (line 3312) +* BFD_RELOC_TILEGX_GLOB_DAT: howto manager. (line 3302) +* BFD_RELOC_TILEGX_HW0: howto manager. (line 3294) +* BFD_RELOC_TILEGX_HW0_LAST: howto manager. (line 3298) +* BFD_RELOC_TILEGX_HW1: howto manager. (line 3295) +* BFD_RELOC_TILEGX_HW1_LAST: howto manager. (line 3299) +* BFD_RELOC_TILEGX_HW2: howto manager. (line 3296) +* BFD_RELOC_TILEGX_HW2_LAST: howto manager. (line 3300) +* BFD_RELOC_TILEGX_HW3: howto manager. (line 3297) +* BFD_RELOC_TILEGX_IMM16_X0_HW0: howto manager. (line 3321) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_GOT: howto manager. (line 3349) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST: howto manager. (line 3329) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_GOT: howto manager. (line 3357) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_PCREL: howto manager. (line 3343) * BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_PLT_PCREL: howto manager. - (line 3101) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_GD: howto manager. (line 3095) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_IE: howto manager. (line 3107) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_LE: howto manager. (line 3091) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_PCREL: howto manager. (line 3059) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_PLT_PCREL: howto manager. (line 3075) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_GD: howto manager. (line 3087) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_IE: howto manager. (line 3099) -* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_LE: howto manager. (line 3089) -* BFD_RELOC_TILEGX_IMM16_X0_HW1: howto manager. (line 3047) -* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST: howto manager. (line 3055) -* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_GOT: howto manager. (line 3083) -* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_PCREL: howto manager. (line 3069) + (line 3377) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_GD: howto manager. (line 3371) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_IE: howto manager. (line 3383) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_LE: howto manager. (line 3367) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_PCREL: howto manager. (line 3335) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_PLT_PCREL: howto manager. (line 3351) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_GD: howto manager. (line 3363) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_IE: howto manager. (line 3375) +* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_LE: howto manager. (line 3365) +* BFD_RELOC_TILEGX_IMM16_X0_HW1: howto manager. (line 3323) +* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST: howto manager. (line 3331) +* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_GOT: howto manager. (line 3359) +* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_PCREL: howto manager. (line 3345) * BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_PLT_PCREL: howto manager. - (line 3103) -* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_GD: howto manager. (line 3097) -* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_IE: howto manager. (line 3109) -* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_LE: howto manager. (line 3093) -* BFD_RELOC_TILEGX_IMM16_X0_HW1_PCREL: howto manager. (line 3061) -* BFD_RELOC_TILEGX_IMM16_X0_HW1_PLT_PCREL: howto manager. (line 3077) -* BFD_RELOC_TILEGX_IMM16_X0_HW2: howto manager. (line 3049) -* BFD_RELOC_TILEGX_IMM16_X0_HW2_LAST: howto manager. (line 3057) -* BFD_RELOC_TILEGX_IMM16_X0_HW2_LAST_PCREL: howto manager. (line 3071) + (line 3379) +* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_GD: howto manager. (line 3373) +* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_IE: howto manager. (line 3385) +* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_LE: howto manager. (line 3369) +* BFD_RELOC_TILEGX_IMM16_X0_HW1_PCREL: howto manager. (line 3337) +* BFD_RELOC_TILEGX_IMM16_X0_HW1_PLT_PCREL: howto manager. (line 3353) +* BFD_RELOC_TILEGX_IMM16_X0_HW2: howto manager. (line 3325) +* BFD_RELOC_TILEGX_IMM16_X0_HW2_LAST: howto manager. (line 3333) +* BFD_RELOC_TILEGX_IMM16_X0_HW2_LAST_PCREL: howto manager. (line 3347) * BFD_RELOC_TILEGX_IMM16_X0_HW2_LAST_PLT_PCREL: howto manager. - (line 3105) -* BFD_RELOC_TILEGX_IMM16_X0_HW2_PCREL: howto manager. (line 3063) -* BFD_RELOC_TILEGX_IMM16_X0_HW2_PLT_PCREL: howto manager. (line 3079) -* BFD_RELOC_TILEGX_IMM16_X0_HW3: howto manager. (line 3051) -* BFD_RELOC_TILEGX_IMM16_X0_HW3_PCREL: howto manager. (line 3065) -* BFD_RELOC_TILEGX_IMM16_X0_HW3_PLT_PCREL: howto manager. (line 3085) -* BFD_RELOC_TILEGX_IMM16_X1_HW0: howto manager. (line 3046) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_GOT: howto manager. (line 3074) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST: howto manager. (line 3054) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_GOT: howto manager. (line 3082) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_PCREL: howto manager. (line 3068) + (line 3381) +* BFD_RELOC_TILEGX_IMM16_X0_HW2_PCREL: howto manager. (line 3339) +* BFD_RELOC_TILEGX_IMM16_X0_HW2_PLT_PCREL: howto manager. (line 3355) +* BFD_RELOC_TILEGX_IMM16_X0_HW3: howto manager. (line 3327) +* BFD_RELOC_TILEGX_IMM16_X0_HW3_PCREL: howto manager. (line 3341) +* BFD_RELOC_TILEGX_IMM16_X0_HW3_PLT_PCREL: howto manager. (line 3361) +* BFD_RELOC_TILEGX_IMM16_X1_HW0: howto manager. (line 3322) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_GOT: howto manager. (line 3350) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST: howto manager. (line 3330) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_GOT: howto manager. (line 3358) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_PCREL: howto manager. (line 3344) * BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_PLT_PCREL: howto manager. - (line 3102) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_GD: howto manager. (line 3096) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_IE: howto manager. (line 3108) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_LE: howto manager. (line 3092) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_PCREL: howto manager. (line 3060) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_PLT_PCREL: howto manager. (line 3076) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_GD: howto manager. (line 3088) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_IE: howto manager. (line 3100) -* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_LE: howto manager. (line 3090) -* BFD_RELOC_TILEGX_IMM16_X1_HW1: howto manager. (line 3048) -* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST: howto manager. (line 3056) -* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_GOT: howto manager. (line 3084) -* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_PCREL: howto manager. (line 3070) + (line 3378) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_GD: howto manager. (line 3372) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_IE: howto manager. (line 3384) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_LE: howto manager. (line 3368) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_PCREL: howto manager. (line 3336) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_PLT_PCREL: howto manager. (line 3352) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_GD: howto manager. (line 3364) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_IE: howto manager. (line 3376) +* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_LE: howto manager. (line 3366) +* BFD_RELOC_TILEGX_IMM16_X1_HW1: howto manager. (line 3324) +* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST: howto manager. (line 3332) +* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_GOT: howto manager. (line 3360) +* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_PCREL: howto manager. (line 3346) * BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_PLT_PCREL: howto manager. - (line 3104) -* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_GD: howto manager. (line 3098) -* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_IE: howto manager. (line 3110) -* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_LE: howto manager. (line 3094) -* BFD_RELOC_TILEGX_IMM16_X1_HW1_PCREL: howto manager. (line 3062) -* BFD_RELOC_TILEGX_IMM16_X1_HW1_PLT_PCREL: howto manager. (line 3078) -* BFD_RELOC_TILEGX_IMM16_X1_HW2: howto manager. (line 3050) -* BFD_RELOC_TILEGX_IMM16_X1_HW2_LAST: howto manager. (line 3058) -* BFD_RELOC_TILEGX_IMM16_X1_HW2_LAST_PCREL: howto manager. (line 3072) + (line 3380) +* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_GD: howto manager. (line 3374) +* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_IE: howto manager. (line 3386) +* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_LE: howto manager. (line 3370) +* BFD_RELOC_TILEGX_IMM16_X1_HW1_PCREL: howto manager. (line 3338) +* BFD_RELOC_TILEGX_IMM16_X1_HW1_PLT_PCREL: howto manager. (line 3354) +* BFD_RELOC_TILEGX_IMM16_X1_HW2: howto manager. (line 3326) +* BFD_RELOC_TILEGX_IMM16_X1_HW2_LAST: howto manager. (line 3334) +* BFD_RELOC_TILEGX_IMM16_X1_HW2_LAST_PCREL: howto manager. (line 3348) * BFD_RELOC_TILEGX_IMM16_X1_HW2_LAST_PLT_PCREL: howto manager. - (line 3106) -* BFD_RELOC_TILEGX_IMM16_X1_HW2_PCREL: howto manager. (line 3064) -* BFD_RELOC_TILEGX_IMM16_X1_HW2_PLT_PCREL: howto manager. (line 3080) -* BFD_RELOC_TILEGX_IMM16_X1_HW3: howto manager. (line 3052) -* BFD_RELOC_TILEGX_IMM16_X1_HW3_PCREL: howto manager. (line 3066) -* BFD_RELOC_TILEGX_IMM16_X1_HW3_PLT_PCREL: howto manager. (line 3086) -* BFD_RELOC_TILEGX_IMM8_X0: howto manager. (line 3032) -* BFD_RELOC_TILEGX_IMM8_X0_TLS_ADD: howto manager. (line 3123) -* BFD_RELOC_TILEGX_IMM8_X0_TLS_GD_ADD: howto manager. (line 3118) -* BFD_RELOC_TILEGX_IMM8_X1: howto manager. (line 3034) -* BFD_RELOC_TILEGX_IMM8_X1_TLS_ADD: howto manager. (line 3124) -* BFD_RELOC_TILEGX_IMM8_X1_TLS_GD_ADD: howto manager. (line 3119) -* BFD_RELOC_TILEGX_IMM8_Y0: howto manager. (line 3033) -* BFD_RELOC_TILEGX_IMM8_Y0_TLS_ADD: howto manager. (line 3125) -* BFD_RELOC_TILEGX_IMM8_Y0_TLS_GD_ADD: howto manager. (line 3120) -* BFD_RELOC_TILEGX_IMM8_Y1: howto manager. (line 3035) -* BFD_RELOC_TILEGX_IMM8_Y1_TLS_ADD: howto manager. (line 3126) -* BFD_RELOC_TILEGX_IMM8_Y1_TLS_GD_ADD: howto manager. (line 3121) -* BFD_RELOC_TILEGX_JMP_SLOT: howto manager. (line 3027) -* BFD_RELOC_TILEGX_JUMPOFF_X1: howto manager. (line 3030) -* BFD_RELOC_TILEGX_JUMPOFF_X1_PLT: howto manager. (line 3031) -* BFD_RELOC_TILEGX_MF_IMM14_X1: howto manager. (line 3038) -* BFD_RELOC_TILEGX_MMEND_X0: howto manager. (line 3040) -* BFD_RELOC_TILEGX_MMSTART_X0: howto manager. (line 3039) -* BFD_RELOC_TILEGX_MT_IMM14_X1: howto manager. (line 3037) -* BFD_RELOC_TILEGX_RELATIVE: howto manager. (line 3028) -* BFD_RELOC_TILEGX_SHAMT_X0: howto manager. (line 3041) -* BFD_RELOC_TILEGX_SHAMT_X1: howto manager. (line 3042) -* BFD_RELOC_TILEGX_SHAMT_Y0: howto manager. (line 3043) -* BFD_RELOC_TILEGX_SHAMT_Y1: howto manager. (line 3044) -* BFD_RELOC_TILEGX_TLS_DTPMOD32: howto manager. (line 3114) -* BFD_RELOC_TILEGX_TLS_DTPMOD64: howto manager. (line 3111) -* BFD_RELOC_TILEGX_TLS_DTPOFF32: howto manager. (line 3115) -* BFD_RELOC_TILEGX_TLS_DTPOFF64: howto manager. (line 3112) -* BFD_RELOC_TILEGX_TLS_GD_CALL: howto manager. (line 3117) -* BFD_RELOC_TILEGX_TLS_IE_LOAD: howto manager. (line 3122) -* BFD_RELOC_TILEGX_TLS_TPOFF32: howto manager. (line 3116) -* BFD_RELOC_TILEGX_TLS_TPOFF64: howto manager. (line 3113) -* BFD_RELOC_TILEPRO_BROFF_X1: howto manager. (line 2941) -* BFD_RELOC_TILEPRO_COPY: howto manager. (line 2937) -* BFD_RELOC_TILEPRO_DEST_IMM8_X1: howto manager. (line 2948) -* BFD_RELOC_TILEPRO_GLOB_DAT: howto manager. (line 2938) -* BFD_RELOC_TILEPRO_IMM16_X0: howto manager. (line 2951) -* BFD_RELOC_TILEPRO_IMM16_X0_GOT: howto manager. (line 2967) -* BFD_RELOC_TILEPRO_IMM16_X0_GOT_HA: howto manager. (line 2973) -* BFD_RELOC_TILEPRO_IMM16_X0_GOT_HI: howto manager. (line 2971) -* BFD_RELOC_TILEPRO_IMM16_X0_GOT_LO: howto manager. (line 2969) -* BFD_RELOC_TILEPRO_IMM16_X0_HA: howto manager. (line 2957) -* BFD_RELOC_TILEPRO_IMM16_X0_HA_PCREL: howto manager. (line 2965) -* BFD_RELOC_TILEPRO_IMM16_X0_HI: howto manager. (line 2955) -* BFD_RELOC_TILEPRO_IMM16_X0_HI_PCREL: howto manager. (line 2963) -* BFD_RELOC_TILEPRO_IMM16_X0_LO: howto manager. (line 2953) -* BFD_RELOC_TILEPRO_IMM16_X0_LO_PCREL: howto manager. (line 2961) -* BFD_RELOC_TILEPRO_IMM16_X0_PCREL: howto manager. (line 2959) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD: howto manager. (line 2989) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_HA: howto manager. (line 2995) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_HI: howto manager. (line 2993) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_LO: howto manager. (line 2991) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE: howto manager. (line 2997) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_HA: howto manager. (line 3003) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_HI: howto manager. (line 3001) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_LO: howto manager. (line 2999) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE: howto manager. (line 3008) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_HA: howto manager. (line 3014) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_HI: howto manager. (line 3012) -* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_LO: howto manager. (line 3010) -* BFD_RELOC_TILEPRO_IMM16_X1: howto manager. (line 2952) -* BFD_RELOC_TILEPRO_IMM16_X1_GOT: howto manager. (line 2968) -* BFD_RELOC_TILEPRO_IMM16_X1_GOT_HA: howto manager. (line 2974) -* BFD_RELOC_TILEPRO_IMM16_X1_GOT_HI: howto manager. (line 2972) -* BFD_RELOC_TILEPRO_IMM16_X1_GOT_LO: howto manager. (line 2970) -* BFD_RELOC_TILEPRO_IMM16_X1_HA: howto manager. (line 2958) -* BFD_RELOC_TILEPRO_IMM16_X1_HA_PCREL: howto manager. (line 2966) -* BFD_RELOC_TILEPRO_IMM16_X1_HI: howto manager. (line 2956) -* BFD_RELOC_TILEPRO_IMM16_X1_HI_PCREL: howto manager. (line 2964) -* BFD_RELOC_TILEPRO_IMM16_X1_LO: howto manager. (line 2954) -* BFD_RELOC_TILEPRO_IMM16_X1_LO_PCREL: howto manager. (line 2962) -* BFD_RELOC_TILEPRO_IMM16_X1_PCREL: howto manager. (line 2960) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD: howto manager. (line 2990) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_HA: howto manager. (line 2996) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_HI: howto manager. (line 2994) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_LO: howto manager. (line 2992) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE: howto manager. (line 2998) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_HA: howto manager. (line 3004) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_HI: howto manager. (line 3002) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_LO: howto manager. (line 3000) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE: howto manager. (line 3009) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_HA: howto manager. (line 3015) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_HI: howto manager. (line 3013) -* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_LO: howto manager. (line 3011) -* BFD_RELOC_TILEPRO_IMM8_X0: howto manager. (line 2944) -* BFD_RELOC_TILEPRO_IMM8_X0_TLS_GD_ADD: howto manager. (line 2984) -* BFD_RELOC_TILEPRO_IMM8_X1: howto manager. (line 2946) -* BFD_RELOC_TILEPRO_IMM8_X1_TLS_GD_ADD: howto manager. (line 2985) -* BFD_RELOC_TILEPRO_IMM8_Y0: howto manager. (line 2945) -* BFD_RELOC_TILEPRO_IMM8_Y0_TLS_GD_ADD: howto manager. (line 2986) -* BFD_RELOC_TILEPRO_IMM8_Y1: howto manager. (line 2947) -* BFD_RELOC_TILEPRO_IMM8_Y1_TLS_GD_ADD: howto manager. (line 2987) -* BFD_RELOC_TILEPRO_JMP_SLOT: howto manager. (line 2939) -* BFD_RELOC_TILEPRO_JOFFLONG_X1: howto manager. (line 2942) -* BFD_RELOC_TILEPRO_JOFFLONG_X1_PLT: howto manager. (line 2943) -* BFD_RELOC_TILEPRO_MF_IMM15_X1: howto manager. (line 2950) -* BFD_RELOC_TILEPRO_MMEND_X0: howto manager. (line 2976) -* BFD_RELOC_TILEPRO_MMEND_X1: howto manager. (line 2978) -* BFD_RELOC_TILEPRO_MMSTART_X0: howto manager. (line 2975) -* BFD_RELOC_TILEPRO_MMSTART_X1: howto manager. (line 2977) -* BFD_RELOC_TILEPRO_MT_IMM15_X1: howto manager. (line 2949) -* BFD_RELOC_TILEPRO_RELATIVE: howto manager. (line 2940) -* BFD_RELOC_TILEPRO_SHAMT_X0: howto manager. (line 2979) -* BFD_RELOC_TILEPRO_SHAMT_X1: howto manager. (line 2980) -* BFD_RELOC_TILEPRO_SHAMT_Y0: howto manager. (line 2981) -* BFD_RELOC_TILEPRO_SHAMT_Y1: howto manager. (line 2982) -* BFD_RELOC_TILEPRO_TLS_DTPMOD32: howto manager. (line 3005) -* BFD_RELOC_TILEPRO_TLS_DTPOFF32: howto manager. (line 3006) -* BFD_RELOC_TILEPRO_TLS_GD_CALL: howto manager. (line 2983) -* BFD_RELOC_TILEPRO_TLS_IE_LOAD: howto manager. (line 2988) -* BFD_RELOC_TILEPRO_TLS_TPOFF32: howto manager. (line 3007) -* bfd_reloc_type_lookup: howto manager. (line 3152) -* BFD_RELOC_V850_16_GOT: howto manager. (line 1385) -* BFD_RELOC_V850_16_GOTOFF: howto manager. (line 1409) -* BFD_RELOC_V850_16_PCREL: howto manager. (line 1355) -* BFD_RELOC_V850_16_S1: howto manager. (line 1373) -* BFD_RELOC_V850_16_SPLIT_OFFSET: howto manager. (line 1370) -* BFD_RELOC_V850_17_PCREL: howto manager. (line 1358) -* BFD_RELOC_V850_22_PCREL: howto manager. (line 1290) -* BFD_RELOC_V850_22_PLT_PCREL: howto manager. (line 1391) -* BFD_RELOC_V850_23: howto manager. (line 1361) -* BFD_RELOC_V850_32_ABS: howto manager. (line 1367) -* BFD_RELOC_V850_32_GOT: howto manager. (line 1388) -* BFD_RELOC_V850_32_GOTOFF: howto manager. (line 1412) -* BFD_RELOC_V850_32_GOTPCREL: howto manager. (line 1382) -* BFD_RELOC_V850_32_PCREL: howto manager. (line 1364) -* BFD_RELOC_V850_32_PLT_PCREL: howto manager. (line 1394) -* BFD_RELOC_V850_9_PCREL: howto manager. (line 1287) -* BFD_RELOC_V850_ALIGN: howto manager. (line 1348) -* BFD_RELOC_V850_CALLT_15_16_OFFSET: howto manager. (line 1379) -* BFD_RELOC_V850_CALLT_16_16_OFFSET: howto manager. (line 1339) -* BFD_RELOC_V850_CALLT_6_7_OFFSET: howto manager. (line 1336) -* BFD_RELOC_V850_CODE: howto manager. (line 1415) -* BFD_RELOC_V850_COPY: howto manager. (line 1397) -* BFD_RELOC_V850_DATA: howto manager. (line 1418) -* BFD_RELOC_V850_GLOB_DAT: howto manager. (line 1400) -* BFD_RELOC_V850_JMP_SLOT: howto manager. (line 1403) -* BFD_RELOC_V850_LO16_S1: howto manager. (line 1376) -* BFD_RELOC_V850_LO16_SPLIT_OFFSET: howto manager. (line 1351) -* BFD_RELOC_V850_LONGCALL: howto manager. (line 1342) -* BFD_RELOC_V850_LONGJUMP: howto manager. (line 1345) -* BFD_RELOC_V850_RELATIVE: howto manager. (line 1406) -* BFD_RELOC_V850_SDA_15_16_OFFSET: howto manager. (line 1296) -* BFD_RELOC_V850_SDA_16_16_OFFSET: howto manager. (line 1293) -* BFD_RELOC_V850_SDA_16_16_SPLIT_OFFSET: howto manager. (line 1328) -* BFD_RELOC_V850_TDA_16_16_OFFSET: howto manager. (line 1318) -* BFD_RELOC_V850_TDA_4_4_OFFSET: howto manager. (line 1325) -* BFD_RELOC_V850_TDA_4_5_OFFSET: howto manager. (line 1321) -* BFD_RELOC_V850_TDA_6_8_OFFSET: howto manager. (line 1307) -* BFD_RELOC_V850_TDA_7_7_OFFSET: howto manager. (line 1315) -* BFD_RELOC_V850_TDA_7_8_OFFSET: howto manager. (line 1311) -* BFD_RELOC_V850_ZDA_15_16_OFFSET: howto manager. (line 1303) -* BFD_RELOC_V850_ZDA_16_16_OFFSET: howto manager. (line 1300) -* BFD_RELOC_V850_ZDA_16_16_SPLIT_OFFSET: howto manager. (line 1332) -* BFD_RELOC_VAX_GLOB_DAT: howto manager. (line 2404) -* BFD_RELOC_VAX_JMP_SLOT: howto manager. (line 2405) -* BFD_RELOC_VAX_RELATIVE: howto manager. (line 2406) -* BFD_RELOC_VPE4KMATH_DATA: howto manager. (line 1980) -* BFD_RELOC_VPE4KMATH_INSN: howto manager. (line 1981) -* BFD_RELOC_VTABLE_ENTRY: howto manager. (line 1985) -* BFD_RELOC_VTABLE_INHERIT: howto manager. (line 1984) -* BFD_RELOC_X86_64_32S: howto manager. (line 607) -* BFD_RELOC_X86_64_COPY: howto manager. (line 602) -* BFD_RELOC_X86_64_DTPMOD64: howto manager. (line 608) -* BFD_RELOC_X86_64_DTPOFF32: howto manager. (line 613) -* BFD_RELOC_X86_64_DTPOFF64: howto manager. (line 609) -* BFD_RELOC_X86_64_GLOB_DAT: howto manager. (line 603) -* BFD_RELOC_X86_64_GOT32: howto manager. (line 600) -* BFD_RELOC_X86_64_GOT64: howto manager. (line 618) -* BFD_RELOC_X86_64_GOTOFF64: howto manager. (line 616) -* BFD_RELOC_X86_64_GOTPC32: howto manager. (line 617) -* BFD_RELOC_X86_64_GOTPC32_TLSDESC: howto manager. (line 623) -* BFD_RELOC_X86_64_GOTPC64: howto manager. (line 620) -* BFD_RELOC_X86_64_GOTPCREL: howto manager. (line 606) -* BFD_RELOC_X86_64_GOTPCREL64: howto manager. (line 619) -* BFD_RELOC_X86_64_GOTPLT64: howto manager. (line 621) -* BFD_RELOC_X86_64_GOTTPOFF: howto manager. (line 614) -* BFD_RELOC_X86_64_IRELATIVE: howto manager. (line 626) -* BFD_RELOC_X86_64_JUMP_SLOT: howto manager. (line 604) -* BFD_RELOC_X86_64_PLT32: howto manager. (line 601) -* BFD_RELOC_X86_64_PLTOFF64: howto manager. (line 622) -* BFD_RELOC_X86_64_RELATIVE: howto manager. (line 605) -* BFD_RELOC_X86_64_TLSDESC: howto manager. (line 625) -* BFD_RELOC_X86_64_TLSDESC_CALL: howto manager. (line 624) -* BFD_RELOC_X86_64_TLSGD: howto manager. (line 611) -* BFD_RELOC_X86_64_TLSLD: howto manager. (line 612) -* BFD_RELOC_X86_64_TPOFF32: howto manager. (line 615) -* BFD_RELOC_X86_64_TPOFF64: howto manager. (line 610) -* BFD_RELOC_XC16X_PAG: howto manager. (line 2398) -* BFD_RELOC_XC16X_POF: howto manager. (line 2399) -* BFD_RELOC_XC16X_SEG: howto manager. (line 2400) -* BFD_RELOC_XC16X_SOF: howto manager. (line 2401) -* BFD_RELOC_XGATE_24: howto manager. (line 2143) -* BFD_RELOC_XGATE_GPAGE: howto manager. (line 2140) -* BFD_RELOC_XGATE_IMM3: howto manager. (line 2160) -* BFD_RELOC_XGATE_IMM4: howto manager. (line 2163) -* BFD_RELOC_XGATE_IMM5: howto manager. (line 2166) -* BFD_RELOC_XGATE_IMM8_HI: howto manager. (line 2156) -* BFD_RELOC_XGATE_IMM8_LO: howto manager. (line 2152) -* BFD_RELOC_XGATE_LO16: howto manager. (line 2136) -* BFD_RELOC_XGATE_PCREL_10: howto manager. (line 2149) -* BFD_RELOC_XGATE_PCREL_9: howto manager. (line 2146) -* BFD_RELOC_XGATE_RL_GROUP: howto manager. (line 2131) -* BFD_RELOC_XGATE_RL_JUMP: howto manager. (line 2127) -* BFD_RELOC_XSTORMY16_12: howto manager. (line 2390) -* BFD_RELOC_XSTORMY16_24: howto manager. (line 2391) -* BFD_RELOC_XSTORMY16_FPTR16: howto manager. (line 2392) -* BFD_RELOC_XSTORMY16_REL_12: howto manager. (line 2389) -* BFD_RELOC_XTENSA_ASM_EXPAND: howto manager. (line 2546) -* BFD_RELOC_XTENSA_ASM_SIMPLIFY: howto manager. (line 2551) -* BFD_RELOC_XTENSA_DIFF16: howto manager. (line 2493) -* BFD_RELOC_XTENSA_DIFF32: howto manager. (line 2494) -* BFD_RELOC_XTENSA_DIFF8: howto manager. (line 2492) -* BFD_RELOC_XTENSA_GLOB_DAT: howto manager. (line 2482) -* BFD_RELOC_XTENSA_JMP_SLOT: howto manager. (line 2483) -* BFD_RELOC_XTENSA_OP0: howto manager. (line 2540) -* BFD_RELOC_XTENSA_OP1: howto manager. (line 2541) -* BFD_RELOC_XTENSA_OP2: howto manager. (line 2542) -* BFD_RELOC_XTENSA_PLT: howto manager. (line 2487) -* BFD_RELOC_XTENSA_RELATIVE: howto manager. (line 2484) -* BFD_RELOC_XTENSA_RTLD: howto manager. (line 2477) -* BFD_RELOC_XTENSA_SLOT0_ALT: howto manager. (line 2522) -* BFD_RELOC_XTENSA_SLOT0_OP: howto manager. (line 2502) -* BFD_RELOC_XTENSA_SLOT10_ALT: howto manager. (line 2532) -* BFD_RELOC_XTENSA_SLOT10_OP: howto manager. (line 2512) -* BFD_RELOC_XTENSA_SLOT11_ALT: howto manager. (line 2533) -* BFD_RELOC_XTENSA_SLOT11_OP: howto manager. (line 2513) -* BFD_RELOC_XTENSA_SLOT12_ALT: howto manager. (line 2534) -* BFD_RELOC_XTENSA_SLOT12_OP: howto manager. (line 2514) -* BFD_RELOC_XTENSA_SLOT13_ALT: howto manager. (line 2535) -* BFD_RELOC_XTENSA_SLOT13_OP: howto manager. (line 2515) -* BFD_RELOC_XTENSA_SLOT14_ALT: howto manager. (line 2536) -* BFD_RELOC_XTENSA_SLOT14_OP: howto manager. (line 2516) -* BFD_RELOC_XTENSA_SLOT1_ALT: howto manager. (line 2523) -* BFD_RELOC_XTENSA_SLOT1_OP: howto manager. (line 2503) -* BFD_RELOC_XTENSA_SLOT2_ALT: howto manager. (line 2524) -* BFD_RELOC_XTENSA_SLOT2_OP: howto manager. (line 2504) -* BFD_RELOC_XTENSA_SLOT3_ALT: howto manager. (line 2525) -* BFD_RELOC_XTENSA_SLOT3_OP: howto manager. (line 2505) -* BFD_RELOC_XTENSA_SLOT4_ALT: howto manager. (line 2526) -* BFD_RELOC_XTENSA_SLOT4_OP: howto manager. (line 2506) -* BFD_RELOC_XTENSA_SLOT5_ALT: howto manager. (line 2527) -* BFD_RELOC_XTENSA_SLOT5_OP: howto manager. (line 2507) -* BFD_RELOC_XTENSA_SLOT6_ALT: howto manager. (line 2528) -* BFD_RELOC_XTENSA_SLOT6_OP: howto manager. (line 2508) -* BFD_RELOC_XTENSA_SLOT7_ALT: howto manager. (line 2529) -* BFD_RELOC_XTENSA_SLOT7_OP: howto manager. (line 2509) -* BFD_RELOC_XTENSA_SLOT8_ALT: howto manager. (line 2530) -* BFD_RELOC_XTENSA_SLOT8_OP: howto manager. (line 2510) -* BFD_RELOC_XTENSA_SLOT9_ALT: howto manager. (line 2531) -* BFD_RELOC_XTENSA_SLOT9_OP: howto manager. (line 2511) -* BFD_RELOC_XTENSA_TLS_ARG: howto manager. (line 2561) -* BFD_RELOC_XTENSA_TLS_CALL: howto manager. (line 2562) -* BFD_RELOC_XTENSA_TLS_DTPOFF: howto manager. (line 2558) -* BFD_RELOC_XTENSA_TLS_FUNC: howto manager. (line 2560) -* BFD_RELOC_XTENSA_TLS_TPOFF: howto manager. (line 2559) -* BFD_RELOC_XTENSA_TLSDESC_ARG: howto manager. (line 2557) -* BFD_RELOC_XTENSA_TLSDESC_FN: howto manager. (line 2556) -* BFD_RELOC_Z80_DISP8: howto manager. (line 2565) -* BFD_RELOC_Z8K_CALLR: howto manager. (line 2571) -* BFD_RELOC_Z8K_DISP7: howto manager. (line 2568) -* BFD_RELOC_Z8K_IMM4L: howto manager. (line 2574) + (line 3382) +* BFD_RELOC_TILEGX_IMM16_X1_HW2_PCREL: howto manager. (line 3340) +* BFD_RELOC_TILEGX_IMM16_X1_HW2_PLT_PCREL: howto manager. (line 3356) +* BFD_RELOC_TILEGX_IMM16_X1_HW3: howto manager. (line 3328) +* BFD_RELOC_TILEGX_IMM16_X1_HW3_PCREL: howto manager. (line 3342) +* BFD_RELOC_TILEGX_IMM16_X1_HW3_PLT_PCREL: howto manager. (line 3362) +* BFD_RELOC_TILEGX_IMM8_X0: howto manager. (line 3308) +* BFD_RELOC_TILEGX_IMM8_X0_TLS_ADD: howto manager. (line 3399) +* BFD_RELOC_TILEGX_IMM8_X0_TLS_GD_ADD: howto manager. (line 3394) +* BFD_RELOC_TILEGX_IMM8_X1: howto manager. (line 3310) +* BFD_RELOC_TILEGX_IMM8_X1_TLS_ADD: howto manager. (line 3400) +* BFD_RELOC_TILEGX_IMM8_X1_TLS_GD_ADD: howto manager. (line 3395) +* BFD_RELOC_TILEGX_IMM8_Y0: howto manager. (line 3309) +* BFD_RELOC_TILEGX_IMM8_Y0_TLS_ADD: howto manager. (line 3401) +* BFD_RELOC_TILEGX_IMM8_Y0_TLS_GD_ADD: howto manager. (line 3396) +* BFD_RELOC_TILEGX_IMM8_Y1: howto manager. (line 3311) +* BFD_RELOC_TILEGX_IMM8_Y1_TLS_ADD: howto manager. (line 3402) +* BFD_RELOC_TILEGX_IMM8_Y1_TLS_GD_ADD: howto manager. (line 3397) +* BFD_RELOC_TILEGX_JMP_SLOT: howto manager. (line 3303) +* BFD_RELOC_TILEGX_JUMPOFF_X1: howto manager. (line 3306) +* BFD_RELOC_TILEGX_JUMPOFF_X1_PLT: howto manager. (line 3307) +* BFD_RELOC_TILEGX_MF_IMM14_X1: howto manager. (line 3314) +* BFD_RELOC_TILEGX_MMEND_X0: howto manager. (line 3316) +* BFD_RELOC_TILEGX_MMSTART_X0: howto manager. (line 3315) +* BFD_RELOC_TILEGX_MT_IMM14_X1: howto manager. (line 3313) +* BFD_RELOC_TILEGX_RELATIVE: howto manager. (line 3304) +* BFD_RELOC_TILEGX_SHAMT_X0: howto manager. (line 3317) +* BFD_RELOC_TILEGX_SHAMT_X1: howto manager. (line 3318) +* BFD_RELOC_TILEGX_SHAMT_Y0: howto manager. (line 3319) +* BFD_RELOC_TILEGX_SHAMT_Y1: howto manager. (line 3320) +* BFD_RELOC_TILEGX_TLS_DTPMOD32: howto manager. (line 3390) +* BFD_RELOC_TILEGX_TLS_DTPMOD64: howto manager. (line 3387) +* BFD_RELOC_TILEGX_TLS_DTPOFF32: howto manager. (line 3391) +* BFD_RELOC_TILEGX_TLS_DTPOFF64: howto manager. (line 3388) +* BFD_RELOC_TILEGX_TLS_GD_CALL: howto manager. (line 3393) +* BFD_RELOC_TILEGX_TLS_IE_LOAD: howto manager. (line 3398) +* BFD_RELOC_TILEGX_TLS_TPOFF32: howto manager. (line 3392) +* BFD_RELOC_TILEGX_TLS_TPOFF64: howto manager. (line 3389) +* BFD_RELOC_TILEPRO_BROFF_X1: howto manager. (line 3217) +* BFD_RELOC_TILEPRO_COPY: howto manager. (line 3213) +* BFD_RELOC_TILEPRO_DEST_IMM8_X1: howto manager. (line 3224) +* BFD_RELOC_TILEPRO_GLOB_DAT: howto manager. (line 3214) +* BFD_RELOC_TILEPRO_IMM16_X0: howto manager. (line 3227) +* BFD_RELOC_TILEPRO_IMM16_X0_GOT: howto manager. (line 3243) +* BFD_RELOC_TILEPRO_IMM16_X0_GOT_HA: howto manager. (line 3249) +* BFD_RELOC_TILEPRO_IMM16_X0_GOT_HI: howto manager. (line 3247) +* BFD_RELOC_TILEPRO_IMM16_X0_GOT_LO: howto manager. (line 3245) +* BFD_RELOC_TILEPRO_IMM16_X0_HA: howto manager. (line 3233) +* BFD_RELOC_TILEPRO_IMM16_X0_HA_PCREL: howto manager. (line 3241) +* BFD_RELOC_TILEPRO_IMM16_X0_HI: howto manager. (line 3231) +* BFD_RELOC_TILEPRO_IMM16_X0_HI_PCREL: howto manager. (line 3239) +* BFD_RELOC_TILEPRO_IMM16_X0_LO: howto manager. (line 3229) +* BFD_RELOC_TILEPRO_IMM16_X0_LO_PCREL: howto manager. (line 3237) +* BFD_RELOC_TILEPRO_IMM16_X0_PCREL: howto manager. (line 3235) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD: howto manager. (line 3265) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_HA: howto manager. (line 3271) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_HI: howto manager. (line 3269) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_LO: howto manager. (line 3267) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE: howto manager. (line 3273) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_HA: howto manager. (line 3279) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_HI: howto manager. (line 3277) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_LO: howto manager. (line 3275) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE: howto manager. (line 3284) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_HA: howto manager. (line 3290) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_HI: howto manager. (line 3288) +* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_LO: howto manager. (line 3286) +* BFD_RELOC_TILEPRO_IMM16_X1: howto manager. (line 3228) +* BFD_RELOC_TILEPRO_IMM16_X1_GOT: howto manager. (line 3244) +* BFD_RELOC_TILEPRO_IMM16_X1_GOT_HA: howto manager. (line 3250) +* BFD_RELOC_TILEPRO_IMM16_X1_GOT_HI: howto manager. (line 3248) +* BFD_RELOC_TILEPRO_IMM16_X1_GOT_LO: howto manager. (line 3246) +* BFD_RELOC_TILEPRO_IMM16_X1_HA: howto manager. (line 3234) +* BFD_RELOC_TILEPRO_IMM16_X1_HA_PCREL: howto manager. (line 3242) +* BFD_RELOC_TILEPRO_IMM16_X1_HI: howto manager. (line 3232) +* BFD_RELOC_TILEPRO_IMM16_X1_HI_PCREL: howto manager. (line 3240) +* BFD_RELOC_TILEPRO_IMM16_X1_LO: howto manager. (line 3230) +* BFD_RELOC_TILEPRO_IMM16_X1_LO_PCREL: howto manager. (line 3238) +* BFD_RELOC_TILEPRO_IMM16_X1_PCREL: howto manager. (line 3236) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD: howto manager. (line 3266) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_HA: howto manager. (line 3272) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_HI: howto manager. (line 3270) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_LO: howto manager. (line 3268) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE: howto manager. (line 3274) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_HA: howto manager. (line 3280) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_HI: howto manager. (line 3278) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_LO: howto manager. (line 3276) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE: howto manager. (line 3285) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_HA: howto manager. (line 3291) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_HI: howto manager. (line 3289) +* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_LO: howto manager. (line 3287) +* BFD_RELOC_TILEPRO_IMM8_X0: howto manager. (line 3220) +* BFD_RELOC_TILEPRO_IMM8_X0_TLS_GD_ADD: howto manager. (line 3260) +* BFD_RELOC_TILEPRO_IMM8_X1: howto manager. (line 3222) +* BFD_RELOC_TILEPRO_IMM8_X1_TLS_GD_ADD: howto manager. (line 3261) +* BFD_RELOC_TILEPRO_IMM8_Y0: howto manager. (line 3221) +* BFD_RELOC_TILEPRO_IMM8_Y0_TLS_GD_ADD: howto manager. (line 3262) +* BFD_RELOC_TILEPRO_IMM8_Y1: howto manager. (line 3223) +* BFD_RELOC_TILEPRO_IMM8_Y1_TLS_GD_ADD: howto manager. (line 3263) +* BFD_RELOC_TILEPRO_JMP_SLOT: howto manager. (line 3215) +* BFD_RELOC_TILEPRO_JOFFLONG_X1: howto manager. (line 3218) +* BFD_RELOC_TILEPRO_JOFFLONG_X1_PLT: howto manager. (line 3219) +* BFD_RELOC_TILEPRO_MF_IMM15_X1: howto manager. (line 3226) +* BFD_RELOC_TILEPRO_MMEND_X0: howto manager. (line 3252) +* BFD_RELOC_TILEPRO_MMEND_X1: howto manager. (line 3254) +* BFD_RELOC_TILEPRO_MMSTART_X0: howto manager. (line 3251) +* BFD_RELOC_TILEPRO_MMSTART_X1: howto manager. (line 3253) +* BFD_RELOC_TILEPRO_MT_IMM15_X1: howto manager. (line 3225) +* BFD_RELOC_TILEPRO_RELATIVE: howto manager. (line 3216) +* BFD_RELOC_TILEPRO_SHAMT_X0: howto manager. (line 3255) +* BFD_RELOC_TILEPRO_SHAMT_X1: howto manager. (line 3256) +* BFD_RELOC_TILEPRO_SHAMT_Y0: howto manager. (line 3257) +* BFD_RELOC_TILEPRO_SHAMT_Y1: howto manager. (line 3258) +* BFD_RELOC_TILEPRO_TLS_DTPMOD32: howto manager. (line 3281) +* BFD_RELOC_TILEPRO_TLS_DTPOFF32: howto manager. (line 3282) +* BFD_RELOC_TILEPRO_TLS_GD_CALL: howto manager. (line 3259) +* BFD_RELOC_TILEPRO_TLS_IE_LOAD: howto manager. (line 3264) +* BFD_RELOC_TILEPRO_TLS_TPOFF32: howto manager. (line 3283) +* bfd_reloc_type_lookup: howto manager. (line 3428) +* BFD_RELOC_V850_16_GOT: howto manager. (line 1567) +* BFD_RELOC_V850_16_GOTOFF: howto manager. (line 1591) +* BFD_RELOC_V850_16_PCREL: howto manager. (line 1537) +* BFD_RELOC_V850_16_S1: howto manager. (line 1555) +* BFD_RELOC_V850_16_SPLIT_OFFSET: howto manager. (line 1552) +* BFD_RELOC_V850_17_PCREL: howto manager. (line 1540) +* BFD_RELOC_V850_22_PCREL: howto manager. (line 1472) +* BFD_RELOC_V850_22_PLT_PCREL: howto manager. (line 1573) +* BFD_RELOC_V850_23: howto manager. (line 1543) +* BFD_RELOC_V850_32_ABS: howto manager. (line 1549) +* BFD_RELOC_V850_32_GOT: howto manager. (line 1570) +* BFD_RELOC_V850_32_GOTOFF: howto manager. (line 1594) +* BFD_RELOC_V850_32_GOTPCREL: howto manager. (line 1564) +* BFD_RELOC_V850_32_PCREL: howto manager. (line 1546) +* BFD_RELOC_V850_32_PLT_PCREL: howto manager. (line 1576) +* BFD_RELOC_V850_9_PCREL: howto manager. (line 1469) +* BFD_RELOC_V850_ALIGN: howto manager. (line 1530) +* BFD_RELOC_V850_CALLT_15_16_OFFSET: howto manager. (line 1561) +* BFD_RELOC_V850_CALLT_16_16_OFFSET: howto manager. (line 1521) +* BFD_RELOC_V850_CALLT_6_7_OFFSET: howto manager. (line 1518) +* BFD_RELOC_V850_CODE: howto manager. (line 1597) +* BFD_RELOC_V850_COPY: howto manager. (line 1579) +* BFD_RELOC_V850_DATA: howto manager. (line 1600) +* BFD_RELOC_V850_GLOB_DAT: howto manager. (line 1582) +* BFD_RELOC_V850_JMP_SLOT: howto manager. (line 1585) +* BFD_RELOC_V850_LO16_S1: howto manager. (line 1558) +* BFD_RELOC_V850_LO16_SPLIT_OFFSET: howto manager. (line 1533) +* BFD_RELOC_V850_LONGCALL: howto manager. (line 1524) +* BFD_RELOC_V850_LONGJUMP: howto manager. (line 1527) +* BFD_RELOC_V850_RELATIVE: howto manager. (line 1588) +* BFD_RELOC_V850_SDA_15_16_OFFSET: howto manager. (line 1478) +* BFD_RELOC_V850_SDA_16_16_OFFSET: howto manager. (line 1475) +* BFD_RELOC_V850_SDA_16_16_SPLIT_OFFSET: howto manager. (line 1510) +* BFD_RELOC_V850_TDA_16_16_OFFSET: howto manager. (line 1500) +* BFD_RELOC_V850_TDA_4_4_OFFSET: howto manager. (line 1507) +* BFD_RELOC_V850_TDA_4_5_OFFSET: howto manager. (line 1503) +* BFD_RELOC_V850_TDA_6_8_OFFSET: howto manager. (line 1489) +* BFD_RELOC_V850_TDA_7_7_OFFSET: howto manager. (line 1497) +* BFD_RELOC_V850_TDA_7_8_OFFSET: howto manager. (line 1493) +* BFD_RELOC_V850_ZDA_15_16_OFFSET: howto manager. (line 1485) +* BFD_RELOC_V850_ZDA_16_16_OFFSET: howto manager. (line 1482) +* BFD_RELOC_V850_ZDA_16_16_SPLIT_OFFSET: howto manager. (line 1514) +* BFD_RELOC_VAX_GLOB_DAT: howto manager. (line 2598) +* BFD_RELOC_VAX_JMP_SLOT: howto manager. (line 2599) +* BFD_RELOC_VAX_RELATIVE: howto manager. (line 2600) +* BFD_RELOC_VPE4KMATH_DATA: howto manager. (line 2174) +* BFD_RELOC_VPE4KMATH_INSN: howto manager. (line 2175) +* BFD_RELOC_VTABLE_ENTRY: howto manager. (line 2179) +* BFD_RELOC_VTABLE_INHERIT: howto manager. (line 2178) +* BFD_RELOC_X86_64_32S: howto manager. (line 608) +* BFD_RELOC_X86_64_COPY: howto manager. (line 603) +* BFD_RELOC_X86_64_DTPMOD64: howto manager. (line 609) +* BFD_RELOC_X86_64_DTPOFF32: howto manager. (line 614) +* BFD_RELOC_X86_64_DTPOFF64: howto manager. (line 610) +* BFD_RELOC_X86_64_GLOB_DAT: howto manager. (line 604) +* BFD_RELOC_X86_64_GOT32: howto manager. (line 601) +* BFD_RELOC_X86_64_GOT64: howto manager. (line 619) +* BFD_RELOC_X86_64_GOTOFF64: howto manager. (line 617) +* BFD_RELOC_X86_64_GOTPC32: howto manager. (line 618) +* BFD_RELOC_X86_64_GOTPC32_TLSDESC: howto manager. (line 624) +* BFD_RELOC_X86_64_GOTPC64: howto manager. (line 621) +* BFD_RELOC_X86_64_GOTPCREL: howto manager. (line 607) +* BFD_RELOC_X86_64_GOTPCREL64: howto manager. (line 620) +* BFD_RELOC_X86_64_GOTPLT64: howto manager. (line 622) +* BFD_RELOC_X86_64_GOTTPOFF: howto manager. (line 615) +* BFD_RELOC_X86_64_IRELATIVE: howto manager. (line 627) +* BFD_RELOC_X86_64_JUMP_SLOT: howto manager. (line 605) +* BFD_RELOC_X86_64_PC32_BND: howto manager. (line 628) +* BFD_RELOC_X86_64_PLT32: howto manager. (line 602) +* BFD_RELOC_X86_64_PLT32_BND: howto manager. (line 629) +* BFD_RELOC_X86_64_PLTOFF64: howto manager. (line 623) +* BFD_RELOC_X86_64_RELATIVE: howto manager. (line 606) +* BFD_RELOC_X86_64_TLSDESC: howto manager. (line 626) +* BFD_RELOC_X86_64_TLSDESC_CALL: howto manager. (line 625) +* BFD_RELOC_X86_64_TLSGD: howto manager. (line 612) +* BFD_RELOC_X86_64_TLSLD: howto manager. (line 613) +* BFD_RELOC_X86_64_TPOFF32: howto manager. (line 616) +* BFD_RELOC_X86_64_TPOFF64: howto manager. (line 611) +* BFD_RELOC_XC16X_PAG: howto manager. (line 2592) +* BFD_RELOC_XC16X_POF: howto manager. (line 2593) +* BFD_RELOC_XC16X_SEG: howto manager. (line 2594) +* BFD_RELOC_XC16X_SOF: howto manager. (line 2595) +* BFD_RELOC_XGATE_24: howto manager. (line 2337) +* BFD_RELOC_XGATE_GPAGE: howto manager. (line 2334) +* BFD_RELOC_XGATE_IMM3: howto manager. (line 2354) +* BFD_RELOC_XGATE_IMM4: howto manager. (line 2357) +* BFD_RELOC_XGATE_IMM5: howto manager. (line 2360) +* BFD_RELOC_XGATE_IMM8_HI: howto manager. (line 2350) +* BFD_RELOC_XGATE_IMM8_LO: howto manager. (line 2346) +* BFD_RELOC_XGATE_LO16: howto manager. (line 2330) +* BFD_RELOC_XGATE_PCREL_10: howto manager. (line 2343) +* BFD_RELOC_XGATE_PCREL_9: howto manager. (line 2340) +* BFD_RELOC_XGATE_RL_GROUP: howto manager. (line 2325) +* BFD_RELOC_XGATE_RL_JUMP: howto manager. (line 2321) +* BFD_RELOC_XSTORMY16_12: howto manager. (line 2584) +* BFD_RELOC_XSTORMY16_24: howto manager. (line 2585) +* BFD_RELOC_XSTORMY16_FPTR16: howto manager. (line 2586) +* BFD_RELOC_XSTORMY16_REL_12: howto manager. (line 2583) +* BFD_RELOC_XTENSA_ASM_EXPAND: howto manager. (line 2755) +* BFD_RELOC_XTENSA_ASM_SIMPLIFY: howto manager. (line 2760) +* BFD_RELOC_XTENSA_DIFF16: howto manager. (line 2702) +* BFD_RELOC_XTENSA_DIFF32: howto manager. (line 2703) +* BFD_RELOC_XTENSA_DIFF8: howto manager. (line 2701) +* BFD_RELOC_XTENSA_GLOB_DAT: howto manager. (line 2691) +* BFD_RELOC_XTENSA_JMP_SLOT: howto manager. (line 2692) +* BFD_RELOC_XTENSA_OP0: howto manager. (line 2749) +* BFD_RELOC_XTENSA_OP1: howto manager. (line 2750) +* BFD_RELOC_XTENSA_OP2: howto manager. (line 2751) +* BFD_RELOC_XTENSA_PLT: howto manager. (line 2696) +* BFD_RELOC_XTENSA_RELATIVE: howto manager. (line 2693) +* BFD_RELOC_XTENSA_RTLD: howto manager. (line 2686) +* BFD_RELOC_XTENSA_SLOT0_ALT: howto manager. (line 2731) +* BFD_RELOC_XTENSA_SLOT0_OP: howto manager. (line 2711) +* BFD_RELOC_XTENSA_SLOT10_ALT: howto manager. (line 2741) +* BFD_RELOC_XTENSA_SLOT10_OP: howto manager. (line 2721) +* BFD_RELOC_XTENSA_SLOT11_ALT: howto manager. (line 2742) +* BFD_RELOC_XTENSA_SLOT11_OP: howto manager. (line 2722) +* BFD_RELOC_XTENSA_SLOT12_ALT: howto manager. (line 2743) +* BFD_RELOC_XTENSA_SLOT12_OP: howto manager. (line 2723) +* BFD_RELOC_XTENSA_SLOT13_ALT: howto manager. (line 2744) +* BFD_RELOC_XTENSA_SLOT13_OP: howto manager. (line 2724) +* BFD_RELOC_XTENSA_SLOT14_ALT: howto manager. (line 2745) +* BFD_RELOC_XTENSA_SLOT14_OP: howto manager. (line 2725) +* BFD_RELOC_XTENSA_SLOT1_ALT: howto manager. (line 2732) +* BFD_RELOC_XTENSA_SLOT1_OP: howto manager. (line 2712) +* BFD_RELOC_XTENSA_SLOT2_ALT: howto manager. (line 2733) +* BFD_RELOC_XTENSA_SLOT2_OP: howto manager. (line 2713) +* BFD_RELOC_XTENSA_SLOT3_ALT: howto manager. (line 2734) +* BFD_RELOC_XTENSA_SLOT3_OP: howto manager. (line 2714) +* BFD_RELOC_XTENSA_SLOT4_ALT: howto manager. (line 2735) +* BFD_RELOC_XTENSA_SLOT4_OP: howto manager. (line 2715) +* BFD_RELOC_XTENSA_SLOT5_ALT: howto manager. (line 2736) +* BFD_RELOC_XTENSA_SLOT5_OP: howto manager. (line 2716) +* BFD_RELOC_XTENSA_SLOT6_ALT: howto manager. (line 2737) +* BFD_RELOC_XTENSA_SLOT6_OP: howto manager. (line 2717) +* BFD_RELOC_XTENSA_SLOT7_ALT: howto manager. (line 2738) +* BFD_RELOC_XTENSA_SLOT7_OP: howto manager. (line 2718) +* BFD_RELOC_XTENSA_SLOT8_ALT: howto manager. (line 2739) +* BFD_RELOC_XTENSA_SLOT8_OP: howto manager. (line 2719) +* BFD_RELOC_XTENSA_SLOT9_ALT: howto manager. (line 2740) +* BFD_RELOC_XTENSA_SLOT9_OP: howto manager. (line 2720) +* BFD_RELOC_XTENSA_TLS_ARG: howto manager. (line 2770) +* BFD_RELOC_XTENSA_TLS_CALL: howto manager. (line 2771) +* BFD_RELOC_XTENSA_TLS_DTPOFF: howto manager. (line 2767) +* BFD_RELOC_XTENSA_TLS_FUNC: howto manager. (line 2769) +* BFD_RELOC_XTENSA_TLS_TPOFF: howto manager. (line 2768) +* BFD_RELOC_XTENSA_TLSDESC_ARG: howto manager. (line 2766) +* BFD_RELOC_XTENSA_TLSDESC_FN: howto manager. (line 2765) +* BFD_RELOC_Z80_DISP8: howto manager. (line 2774) +* BFD_RELOC_Z8K_CALLR: howto manager. (line 2780) +* BFD_RELOC_Z8K_DISP7: howto manager. (line 2777) +* BFD_RELOC_Z8K_IMM4L: howto manager. (line 2783) * bfd_rename_section: section prototypes. (line 169) -* bfd_scan_arch: Architectures. (line 486) +* bfd_scan_arch: Architectures. (line 506) * bfd_scan_vma: Miscellaneous. (line 124) * bfd_seach_for_target: bfd_target. (line 524) * bfd_section_already_linked: Writing the symbol table. (line 55) * bfd_section_list_clear: section prototypes. (line 8) * bfd_sections_find_if: section prototypes. (line 199) -* bfd_set_arch_info: Architectures. (line 527) +* bfd_set_arch_info: Architectures. (line 547) * bfd_set_archive_head: Archives. (line 75) * bfd_set_assert_handler: Error reporting. (line 141) * bfd_set_default_target: bfd_target. (line 463) @@ -12978,21 +13476,23 @@ BFD Index * bfd_target_list: bfd_target. (line 515) * bfd_write_bigendian_4byte_int: Internal. (line 13) * bfd_zalloc: Opening and Closing. - (line 236) + (line 257) * bfd_zalloc2: Opening and Closing. - (line 245) + (line 266) * coff_symbol_type: coff. (line 245) * core_file_matches_executable_p: Core Files. (line 39) * find_separate_debug_file: Opening and Closing. - (line 288) + (line 332) * generic_core_file_matches_executable_p: Core Files. (line 49) * Hash tables: Hash Tables. (line 6) * internal object-file format: Canonical format. (line 11) * Linker: Linker Functions. (line 6) * Other functions: Miscellaneous. (line 206) +* separate_alt_debug_file_exists: Opening and Closing. + (line 323) * separate_debug_file_exists: Opening and Closing. - (line 279) -* struct bfd_iovec: Miscellaneous. (line 378) + (line 314) +* struct bfd_iovec: Miscellaneous. (line 370) * target vector (_bfd_final_link): Performing the Final Link. (line 6) * target vector (_bfd_link_add_symbols): Adding Symbols to the Hash Table. @@ -13005,70 +13505,70 @@ BFD Index Tag Table: -Node: Top1182 -Node: Overview1521 -Node: History2572 -Node: How It Works3518 -Node: What BFD Version 2 Can Do5061 -Node: BFD information loss6376 -Node: Canonical format8908 -Node: BFD front end13280 -Node: typedef bfd13704 -Node: Error reporting24749 -Node: Miscellaneous29616 -Node: Memory Usage46984 -Node: Initialization48212 -Node: Sections48671 -Node: Section Input49154 -Node: Section Output50519 -Node: typedef asection53005 -Node: section prototypes78341 -Node: Symbols88598 -Node: Reading Symbols90193 -Node: Writing Symbols91300 -Node: Mini Symbols93041 -Node: typedef asymbol94015 -Node: symbol handling functions100254 -Node: Archives105596 -Node: Formats109625 -Node: Relocations112573 -Node: typedef arelent113300 -Node: howto manager128936 -Node: Core Files231991 -Node: Targets234029 -Node: bfd_target235999 -Node: Architectures259221 -Node: Opening and Closing285391 -Node: Internal297409 -Node: File Caching303754 -Node: Linker Functions305668 -Node: Creating a Linker Hash Table307341 -Node: Adding Symbols to the Hash Table309079 -Node: Differing file formats309979 -Node: Adding symbols from an object file311704 -Node: Adding symbols from an archive313855 -Node: Performing the Final Link316784 -Node: Information provided by the linker318026 -Node: Relocating the section contents319180 -Node: Writing the symbol table320931 -Node: Hash Tables325315 -Node: Creating and Freeing a Hash Table326513 -Node: Looking Up or Entering a String327763 -Node: Traversing a Hash Table329016 -Node: Deriving a New Hash Table Type329805 -Node: Define the Derived Structures330871 -Node: Write the Derived Creation Routine331952 -Node: Write Other Derived Routines334576 -Node: BFD back ends335891 -Node: What to Put Where336161 -Node: aout336341 -Node: coff342659 -Node: elf371096 -Node: mmo371497 -Node: File layout372425 -Node: Symbol-table378072 -Node: mmo section mapping381841 -Node: GNU Free Documentation License385493 -Node: BFD Index410576 +Node: Top1172 +Node: Overview1511 +Node: History2562 +Node: How It Works3508 +Node: What BFD Version 2 Can Do5051 +Node: BFD information loss6366 +Node: Canonical format8898 +Node: BFD front end13270 +Node: typedef bfd13694 +Node: Error reporting24615 +Node: Miscellaneous29482 +Node: Memory Usage46625 +Node: Initialization47853 +Node: Sections48312 +Node: Section Input48795 +Node: Section Output50160 +Node: typedef asection52646 +Node: section prototypes78790 +Node: Symbols89047 +Node: Reading Symbols90642 +Node: Writing Symbols91749 +Node: Mini Symbols93490 +Node: typedef asymbol94464 +Node: symbol handling functions100523 +Node: Archives105865 +Node: Formats109894 +Node: Relocations112842 +Node: typedef arelent113569 +Node: howto manager129205 +Node: Core Files241456 +Node: Targets243494 +Node: bfd_target245464 +Node: Architectures268686 +Node: Opening and Closing295795 +Node: Internal310117 +Node: File Caching316462 +Node: Linker Functions318376 +Node: Creating a Linker Hash Table320049 +Node: Adding Symbols to the Hash Table321787 +Node: Differing file formats322687 +Node: Adding symbols from an object file324412 +Node: Adding symbols from an archive326563 +Node: Performing the Final Link329492 +Node: Information provided by the linker330734 +Node: Relocating the section contents331888 +Node: Writing the symbol table333639 +Node: Hash Tables338023 +Node: Creating and Freeing a Hash Table339221 +Node: Looking Up or Entering a String340471 +Node: Traversing a Hash Table341724 +Node: Deriving a New Hash Table Type342513 +Node: Define the Derived Structures343579 +Node: Write the Derived Creation Routine344660 +Node: Write Other Derived Routines347284 +Node: BFD back ends348599 +Node: What to Put Where348869 +Node: aout349049 +Node: coff355367 +Node: elf383804 +Node: mmo384205 +Node: File layout385133 +Node: Symbol-table390780 +Node: mmo section mapping394549 +Node: GNU Free Documentation License398201 +Node: BFD Index423284 End Tag Table diff --git a/share/info/configure.info b/share/info/configure.info index dc75d62..360084a 100644 --- a/share/info/configure.info +++ b/share/info/configure.info @@ -1,12 +1,12 @@ -This is configure.info, produced by makeinfo version 4.13 from -/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/../build/../binutils/binutils-current/etc/configure.texi. +This is configure.info, produced by makeinfo version 5.1 from +configure.texi. INFO-DIR-SECTION GNU admin START-INFO-DIR-ENTRY * configure: (configure). The GNU configure and build system END-INFO-DIR-ENTRY - This file documents the GNU configure and build system. +This file documents the GNU configure and build system. Copyright (C) 1998 Cygnus Solutions. @@ -15,8 +15,8 @@ manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of -this manual under the conditions for verbatim copying, provided that -the entire resulting derived work is distributed under the terms of a +this manual under the conditions for verbatim copying, provided 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 @@ -56,17 +56,17 @@ describes how autoconf, automake, libtool, and make fit together. It also includes a discussion of the older Cygnus configure system. This document does not describe in detail how to use each of the -tools; see the respective manuals for that. Instead, it describes -which files the developer must write, which files are machine generated -and how they are generated, and where certain common problems should be +tools; see the respective manuals for that. Instead, it describes which +files the developer must write, which files are machine generated and +how they are generated, and where certain common problems should be addressed. - This document draws on several sources, including the autoconf -manual by David MacKenzie (*note autoconf overview: (autoconf)Top.), -the automake manual by David MacKenzie and Tom Tromey (*note automake + This document draws on several sources, including the autoconf manual +by David MacKenzie (*note autoconf overview: (autoconf)Top.), the +automake manual by David MacKenzie and Tom Tromey (*note automake overview: (automake)Top.), the libtool manual by Gordon Matzigkeit -(*note libtool overview: (libtool)Top.), and the Cygnus configure -manual by K. Richard Pixley. +(*note libtool overview: (libtool)Top.), and the Cygnus configure manual +by K. Richard Pixley. * Menu: @@ -110,22 +110,17 @@ program, and a C compiler. autoconf provides a general portability framework, based on testing the features of the host system at build time. - automake a system for describing how to build a program, permitting the - developer to write a simplified `Makefile'. - + developer to write a simplified 'Makefile'. libtool a standardized approach to building shared libraries. - gettext provides a framework for translation of text messages into other languages; not really discussed in this document. - m4 autoconf requires the GNU version of m4; the standard Unix m4 does not suffice. - perl automake requires perl. @@ -139,28 +134,26 @@ This is a very brief and probably inaccurate history. As the number of Unix variants increased during the 1980s, it became harder to write programs which could run on all variants. While it was -often possible to use `#ifdef' to identify particular systems, +often possible to use '#ifdef' to identify particular systems, developers frequently did not have access to every system, and the characteristics of some systems changed from version to version. By 1992, at least three different approaches had been developed: * The Metaconfig program, by Larry Wall, Harlan Stenn, and Raphael Manfredi. - * The Cygnus configure script, by K. Richard Pixley, and the gcc configure script, by Richard Stallman. These use essentially the same approach, and the developers communicated regularly. - * The autoconf program, by David MacKenzie. The Metaconfig program is still used for Perl and a few other -programs. It is part of the Dist package. I do not know if it is -being developed. +programs. It is part of the Dist package. I do not know if it is being +developed. In 1994, David MacKenzie and others modified autoconf to incorporate -all the features of Cygnus configure. Since then, there has been a -slow but steady conversion of GNU programs from Cygnus configure to -autoconf. gcc has been converted, eliminating the gcc configure script. +all the features of Cygnus configure. Since then, there has been a slow +but steady conversion of GNU programs from Cygnus configure to autoconf. +gcc has been converted, eliminating the gcc configure script. GNU autoconf was regularly maintained until late 1996. As of this writing in June, 1998, it has no public maintainer. @@ -203,68 +196,65 @@ File: configure.info, Node: Building, Prev: History, Up: Introduction ============ Most readers of this document should already know how to build a tool by -running `configure' and `make'. This section may serve as a quick +running 'configure' and 'make'. This section may serve as a quick introduction or reminder. - Building a tool is normally as simple as running `configure' -followed by `make'. You should normally run `configure' from an empty -directory, using some path to refer to the `configure' script in the -source directory. The directory in which you run `configure' is called -the "object directory". + Building a tool is normally as simple as running 'configure' followed +by 'make'. You should normally run 'configure' from an empty directory, +using some path to refer to the 'configure' script in the source +directory. The directory in which you run 'configure' is called the +"object directory". In order to use a object directory which is different from the source -directory, you must be using the GNU version of `make', which has the -required `VPATH' support. Despite this restriction, using a different +directory, you must be using the GNU version of 'make', which has the +required 'VPATH' support. Despite this restriction, using a different object directory is highly recommended: * It keeps the files generated during the build from cluttering up your sources. - * It permits you to remove the built files by simply removing the entire build directory. - * It permits you to build from the same sources with several sets of configure options simultaneously. - If you don't have GNU `make', you will have to run `configure' in -the source directory. All GNU packages should support this; in -particular, GNU packages should not assume the presence of GNU `make'. + If you don't have GNU 'make', you will have to run 'configure' in the +source directory. All GNU packages should support this; in particular, +GNU packages should not assume the presence of GNU 'make'. - After running `configure', you can build the tools by running `make'. + After running 'configure', you can build the tools by running 'make'. - To install the tools, run `make install'. Installing the tools will + To install the tools, run 'make install'. Installing the tools will copy the programs and any required support files to the "installation -directory". The location of the installation directory is controlled -by `configure' options, as described below. - - In the Cygnus tree at present, the info files are built and -installed as a separate step. To build them, run `make info'. To -install them, run `make install-info'. The equivalent html files are -also built and installed in a separate step. To build the html files, -run `make html'. To install the html files run `make install-html'. - - All `configure' scripts support a wide variety of options. The most -interesting ones are `--with' and `--enable' options which are -generally specific to particular tools. You can usually use the -`--help' option to get a list of interesting options for a particular -configure script. - - The only generic options you are likely to use are the `--prefix' -and `--exec-prefix' options. These options are used to specify the +directory". The location of the installation directory is controlled by +'configure' options, as described below. + + In the Cygnus tree at present, the info files are built and installed +as a separate step. To build them, run 'make info'. To install them, +run 'make install-info'. The equivalent html files are also built and +installed in a separate step. To build the html files, run 'make html'. +To install the html files run 'make install-html'. + + All 'configure' scripts support a wide variety of options. The most +interesting ones are '--with' and '--enable' options which are generally +specific to particular tools. You can usually use the '--help' option +to get a list of interesting options for a particular configure script. + + The only generic options you are likely to use are the '--prefix' and +'--exec-prefix' options. These options are used to specify the installation directory. - The directory named by the `--prefix' option will hold machine + The directory named by the '--prefix' option will hold machine independent files such as info files. - The directory named by the `--exec-prefix' option, which is normally -a subdirectory of the `--prefix' directory, will hold machine dependent + The directory named by the '--exec-prefix' option, which is normally +a subdirectory of the '--prefix' directory, will hold machine dependent files such as executables. - The default for `--prefix' is `/usr/local'. The default for -`--exec-prefix' is the value used for `--prefix'. + The default for '--prefix' is '/usr/local'. The default for +'--exec-prefix' is the value used for '--prefix'. - The convention used in Cygnus releases is to use a `--prefix' option -of `/usr/cygnus/RELEASE', where RELEASE is the name of the release, and -to use a `--exec-prefix' option of `/usr/cygnus/RELEASE/H-HOST', where + The convention used in Cygnus releases is to use a '--prefix' option +of '/usr/cygnus/RELEASE', where RELEASE is the name of the release, and +to use a '--exec-prefix' option of '/usr/cygnus/RELEASE/H-HOST', where HOST is the configuration name of the host system (*note Configuration Names::). @@ -295,74 +285,72 @@ File: configure.info, Node: Write configure.in, Next: Write Makefile.am, Up: 2.1 Write configure.in ====================== -You must first write the file `configure.in'. This is an autoconf -input file, and the autoconf manual describes in detail what this file -should look like. +You must first write the file 'configure.in'. This is an autoconf input +file, and the autoconf manual describes in detail what this file should +look like. - You will write tests in your `configure.in' file to check for + You will write tests in your 'configure.in' file to check for conditions that may change from one system to another, such as the presence of particular header files or functions. - For example, not all systems support the `gettimeofday' function. -If you want to use the `gettimeofday' function when it is available, -and to use some other function when it is not, you would check for this -by putting `AC_CHECK_FUNCS(gettimeofday)' in `configure.in'. + For example, not all systems support the 'gettimeofday' function. If +you want to use the 'gettimeofday' function when it is available, and to +use some other function when it is not, you would check for this by +putting 'AC_CHECK_FUNCS(gettimeofday)' in 'configure.in'. When the configure script is run at build time, this will arrange to -define the preprocessor macro `HAVE_GETTIMEOFDAY' to the value 1 if the -`gettimeofday' function is available, and to not define the macro at -all if the function is not available. Your code can then use `#ifdef' -to test whether it is safe to call `gettimeofday'. +define the preprocessor macro 'HAVE_GETTIMEOFDAY' to the value 1 if the +'gettimeofday' function is available, and to not define the macro at all +if the function is not available. Your code can then use '#ifdef' to +test whether it is safe to call 'gettimeofday'. - If you have an existing body of code, the `autoscan' program may -help identify potential portability problems, and hence configure tests -that you will want to use. *Note Invoking autoscan: (autoconf)Invoking -autoscan. + If you have an existing body of code, the 'autoscan' program may help +identify potential portability problems, and hence configure tests that +you will want to use. *Note (autoconf)Invoking autoscan::. - Another handy tool for an existing body of code is `ifnames'. This + Another handy tool for an existing body of code is 'ifnames'. This will show you all the preprocessor conditionals that the code already -uses. *Note Invoking ifnames: (autoconf)Invoking ifnames. +uses. *Note (autoconf)Invoking ifnames::. Besides the portability tests which are specific to your particular -package, every `configure.in' file should contain the following macros. +package, every 'configure.in' file should contain the following macros. -`AC_INIT' +'AC_INIT' This macro takes a single argument, which is the name of a file in - your package. For example, `AC_INIT(foo.c)'. + your package. For example, 'AC_INIT(foo.c)'. -`AC_PREREQ(VERSION)' +'AC_PREREQ(VERSION)' This macro is optional. It may be used to indicate the version of - `autoconf' that you are using. This will prevent users from - running an earlier version of `autoconf' and perhaps getting an - invalid `configure' script. For example, `AC_PREREQ(2.12)'. + 'autoconf' that you are using. This will prevent users from + running an earlier version of 'autoconf' and perhaps getting an + invalid 'configure' script. For example, 'AC_PREREQ(2.12)'. -`AM_INIT_AUTOMAKE' +'AM_INIT_AUTOMAKE' This macro takes two arguments: the name of the package, and a - version number. For example, `AM_INIT_AUTOMAKE(foo, 1.0)'. (This + version number. For example, 'AM_INIT_AUTOMAKE(foo, 1.0)'. (This macro is not needed if you are not using automake). -`AM_CONFIG_HEADER' +'AM_CONFIG_HEADER' This macro names the header file which will hold the preprocessor - macro definitions at run time. Normally this should be - `config.h'. Your sources would then use `#include "config.h"' to - include it. + macro definitions at run time. Normally this should be 'config.h'. + Your sources would then use '#include "config.h"' to include it. - This macro may optionally name the input file for that header - file; by default, this is `config.h.in', but that file name works - poorly on DOS filesystems. Therefore, it is often better to name - it explicitly as `config.in'. + This macro may optionally name the input file for that header file; + by default, this is 'config.h.in', but that file name works poorly + on DOS filesystems. Therefore, it is often better to name it + explicitly as 'config.in'. - This is what you should normally put in `configure.in': + This is what you should normally put in 'configure.in': AM_CONFIG_HEADER(config.h:config.in) - (If you are not using automake, use `AC_CONFIG_HEADER' rather than - `AM_CONFIG_HEADER'). + (If you are not using automake, use 'AC_CONFIG_HEADER' rather than + 'AM_CONFIG_HEADER'). -`AM_MAINTAINER_MODE' +'AM_MAINTAINER_MODE' This macro always appears in Cygnus configure scripts. Other programs may or may not use it. - If this macro is used, the `--enable-maintainer-mode' option is + If this macro is used, the '--enable-maintainer-mode' option is required to enable automatic rebuilding of generated files used by the configure system. This of course requires that developers be aware of, and use, that option. @@ -370,47 +358,47 @@ package, every `configure.in' file should contain the following macros. If this macro is not used, then the generated files will always be rebuilt automatically. This will cause problems if the wrong versions of autoconf, automake, or others are in the builder's - `PATH'. + 'PATH'. (If you are not using automake, you do not need to use this macro). -`AC_EXEEXT' - Either this macro or `AM_EXEEXT' always appears in Cygnus configure +'AC_EXEEXT' + Either this macro or 'AM_EXEEXT' always appears in Cygnus configure files. Other programs may or may not use one of them. - This macro looks for the executable suffix used on the host - system. On Unix systems, this is the empty string. On Windows - systems, this is `.exe'. This macro directs automake to use the - executable suffix as appropriate when creating programs. This - macro does not take any arguments. + This macro looks for the executable suffix used on the host system. + On Unix systems, this is the empty string. On Windows systems, + this is '.exe'. This macro directs automake to use the executable + suffix as appropriate when creating programs. This macro does not + take any arguments. - The `AC_EXEEXT' form is new, and is part of a Cygnus patch to + The 'AC_EXEEXT' form is new, and is part of a Cygnus patch to autoconf to support compiling with Visual C++. Older programs use - `AM_EXEEXT' instead. + 'AM_EXEEXT' instead. - (Programs which do not use automake use neither `AC_EXEEXT' nor - `AM_EXEEXT'). + (Programs which do not use automake use neither 'AC_EXEEXT' nor + 'AM_EXEEXT'). -`AC_PROG_CC' +'AC_PROG_CC' If you are writing C code, you will normally want to use this macro. It locates the C compiler to use. It does not take any arguments. - However, if this `configure.in' file is for a library which is to + However, if this 'configure.in' file is for a library which is to be compiled by a cross compiler which may not fully work, then you - will not want to use `AC_PROG_CC'. Instead, you will want to use a - variant which does not call the macro `AC_PROG_CC_WORKS'. Examples - can be found in various `configure.in' files for libraries that are - compiled with cross compilers, such as libiberty or libgloss. - This is essentially a bug in autoconf, and there will probably be - a better workaround at some point. - -`AC_PROG_CXX' + will not want to use 'AC_PROG_CC'. Instead, you will want to use a + variant which does not call the macro 'AC_PROG_CC_WORKS'. Examples + can be found in various 'configure.in' files for libraries that are + compiled with cross compilers, such as libiberty or libgloss. This + is essentially a bug in autoconf, and there will probably be a + better workaround at some point. + +'AC_PROG_CXX' If you are writing C++ code, you will want to use this macro. It locates the C++ compiler to use. It does not take any arguments. - The same cross compiler comments apply as for `AC_PROG_CC'. + The same cross compiler comments apply as for 'AC_PROG_CC'. -`AM_PROG_LIBTOOL' +'AM_PROG_LIBTOOL' If you want to build libraries, and you want to permit them to be shared, or you want to link against libraries which were built using libtool, then you will need this macro. This macro is @@ -418,36 +406,36 @@ package, every `configure.in' file should contain the following macros. By default, this will cause all libraries to be built as shared libraries. To prevent this-to change the default-use - `AM_DISABLE_SHARED' before `AM_PROG_LIBTOOL'. The configure - options `--enable-shared' and `--disable-shared' may be used to + 'AM_DISABLE_SHARED' before 'AM_PROG_LIBTOOL'. The configure + options '--enable-shared' and '--disable-shared' may be used to override the default at build time. -`AC_DEFINE(_GNU_SOURCE)' +'AC_DEFINE(_GNU_SOURCE)' GNU packages should normally include this line before any other - feature tests. This defines the macro `_GNU_SOURCE' when + feature tests. This defines the macro '_GNU_SOURCE' when compiling, which directs the libc header files to provide the standard GNU system interfaces including all GNU extensions. If this macro is not defined, certain GNU extensions may not be available. -`AC_OUTPUT' +'AC_OUTPUT' This macro takes a list of file names which the configure process - should produce. This is normally a list of one or more `Makefile' + should produce. This is normally a list of one or more 'Makefile' files in different directories. If your package lives entirely in - a single directory, you would use simply `AC_OUTPUT(Makefile)'. - If you also have, for example, a `lib' subdirectory, you would use - `AC_OUTPUT(Makefile lib/Makefile)'. + a single directory, you would use simply 'AC_OUTPUT(Makefile)'. If + you also have, for example, a 'lib' subdirectory, you would use + 'AC_OUTPUT(Makefile lib/Makefile)'. - If you want to use locally defined macros in your `configure.in' -file, then you will need to write a `acinclude.m4' file which defines -them (if not using automake, this file is called `aclocal.m4'). -Alternatively, you can put separate macros in an `m4' subdirectory, and -put `ACLOCAL_AMFLAGS = -I m4' in your `Makefile.am' file so that the -`aclocal' program will be able to find them. + If you want to use locally defined macros in your 'configure.in' +file, then you will need to write a 'acinclude.m4' file which defines +them (if not using automake, this file is called 'aclocal.m4'). +Alternatively, you can put separate macros in an 'm4' subdirectory, and +put 'ACLOCAL_AMFLAGS = -I m4' in your 'Makefile.am' file so that the +'aclocal' program will be able to find them. The different macro prefixes indicate which tool defines the macro. -Macros which start with `AC_' are part of autoconf. Macros which start -with `AM_' are provided by automake or libtool. +Macros which start with 'AC_' are part of autoconf. Macros which start +with 'AM_' are provided by automake or libtool. File: configure.info, Node: Write Makefile.am, Next: Write acconfig.h, Prev: Write configure.in, Up: Getting Started @@ -455,71 +443,70 @@ File: configure.info, Node: Write Makefile.am, Next: Write acconfig.h, Prev: 2.2 Write Makefile.am ===================== -You must write the file `Makefile.am'. This is an automake input file, +You must write the file 'Makefile.am'. This is an automake input file, and the automake manual describes in detail what this file should look like. - The automake commands in `Makefile.am' mostly look like variable -assignments in a `Makefile'. automake recognizes special variable + The automake commands in 'Makefile.am' mostly look like variable +assignments in a 'Makefile'. automake recognizes special variable names, and automatically add make rules to the output as needed. - There will be one `Makefile.am' file for each directory in your -package. For each directory with subdirectories, the `Makefile.am' -file should contain the line + There will be one 'Makefile.am' file for each directory in your +package. For each directory with subdirectories, the 'Makefile.am' file +should contain the line SUBDIRS = DIR DIR ... - where each DIR is the name of a subdirectory. +where each DIR is the name of a subdirectory. - For each `Makefile.am', there should be a corresponding `Makefile' -in the `AC_OUTPUT' macro in `configure.in'. + For each 'Makefile.am', there should be a corresponding 'Makefile' in +the 'AC_OUTPUT' macro in 'configure.in'. - Every `Makefile.am' written at Cygnus should contain the line + Every 'Makefile.am' written at Cygnus should contain the line AUTOMAKE_OPTIONS = cygnus - This puts automake into Cygnus mode. See the automake manual for +This puts automake into Cygnus mode. See the automake manual for details. - You may to include the version number of `automake' that you are -using on the `AUTOMAKE_OPTIONS' line. For example, + You may to include the version number of 'automake' that you are +using on the 'AUTOMAKE_OPTIONS' line. For example, AUTOMAKE_OPTIONS = cygnus 1.3 - This will prevent users from running an earlier version of -`automake' and perhaps getting an invalid `Makefile.in'. +This will prevent users from running an earlier version of 'automake' +and perhaps getting an invalid 'Makefile.in'. If your package builds a program, then in the directory where that program is built you will normally want a line like bin_PROGRAMS = PROGRAM - where PROGRAM is the name of the program. You will then want a line +where PROGRAM is the name of the program. You will then want a line like PROGRAM_SOURCES = FILE FILE ... - where each FILE is the name of a source file to link into the -program (e.g., `foo.c'). +where each FILE is the name of a source file to link into the program +(e.g., 'foo.c'). If your package builds a library, and you do not want the library to ever be built as a shared library, then in the directory where that library is built you will normally want a line like lib_LIBRARIES = libNAME.a - where `libNAME.a' is the name of the library. You will then want a -line like +where 'libNAME.a' is the name of the library. You will then want a line +like libNAME_a_SOURCES = FILE FILE ... - where each FILE is the name of a source file to add to the library. +where each FILE is the name of a source file to add to the library. If your package builds a library, and you want to permit building the library as a shared library, then in the directory where that library is built you will normally want a line like lib_LTLIBRARIES = libNAME.la - The use of `LTLIBRARIES', and the `.la' extension, indicate a -library to be built using libtool. As usual, you will then want a line -like + The use of 'LTLIBRARIES', and the '.la' extension, indicate a library +to be built using libtool. As usual, you will then want a line like libNAME_la_SOURCES = FILE FILE ... - The strings `bin' and `lib' that appear above in `bin_PROGRAMS' and -`lib_LIBRARIES' are not arbitrary. They refer to particular -directories, which may be set by the `--bindir' and `--libdir' options -to `configure'. If those options are not used, the default values are -based on the `--prefix' or `--exec-prefix' options to `configure'. It + The strings 'bin' and 'lib' that appear above in 'bin_PROGRAMS' and +'lib_LIBRARIES' are not arbitrary. They refer to particular +directories, which may be set by the '--bindir' and '--libdir' options +to 'configure'. If those options are not used, the default values are +based on the '--prefix' or '--exec-prefix' options to 'configure'. It is possible to use other names if the program or library should be installed in some other directory. - The `Makefile.am' file may also contain almost anything that may -appear in a normal `Makefile'. automake also supports many other + The 'Makefile.am' file may also contain almost anything that may +appear in a normal 'Makefile'. automake also supports many other special variables, as well as conditionals. See the automake manual for more information. @@ -531,8 +518,8 @@ File: configure.info, Node: Write acconfig.h, Next: Generate files, Prev: Wri ==================== If you are generating a portability header file, (i.e., you are using -`AM_CONFIG_HEADER' in `configure.in'), then you will have to write a -`acconfig.h' file. It will have to contain the following lines. +'AM_CONFIG_HEADER' in 'configure.in'), then you will have to write a +'acconfig.h' file. It will have to contain the following lines. /* Name of package. */ #undef PACKAGE @@ -543,26 +530,26 @@ If you are generating a portability header file, (i.e., you are using This requirement is really a bug in the system, and the requirement may be eliminated at some later date. - The `acconfig.h' file will also similar comment and `#undef' lines -for any unusual macros in the `configure.in' file, including any macro -which appears in a `AC_DEFINE' macro. + The 'acconfig.h' file will also similar comment and '#undef' lines +for any unusual macros in the 'configure.in' file, including any macro +which appears in a 'AC_DEFINE' macro. In particular, if you are writing a GNU package and therefore include -`AC_DEFINE(_GNU_SOURCE)' in `configure.in' as suggested above, you will -need lines like this in `acconfig.h': +'AC_DEFINE(_GNU_SOURCE)' in 'configure.in' as suggested above, you will +need lines like this in 'acconfig.h': /* Enable GNU extensions. */ #undef _GNU_SOURCE - Normally the `autoheader' program will inform you of any such + Normally the 'autoheader' program will inform you of any such requirements by printing an error message when it is run. However, if -you do anything particular odd in your `configure.in' file, you will -have to make sure that the right entries appear in `acconfig.h', since +you do anything particular odd in your 'configure.in' file, you will +have to make sure that the right entries appear in 'acconfig.h', since otherwise the results of the tests may not be available in the -`config.h' file which your code will use. +'config.h' file which your code will use. - (Thee `PACKAGE' and `VERSION' lines are not required if you are not -using automake, and in that case you may not need a `acconfig.h' file -at all). + (Thee 'PACKAGE' and 'VERSION' lines are not required if you are not +using automake, and in that case you may not need a 'acconfig.h' file at +all). File: configure.info, Node: Generate files, Next: Getting Started Example, Prev: Write acconfig.h, Up: Getting Started @@ -570,8 +557,8 @@ File: configure.info, Node: Generate files, Next: Getting Started Example, Pr 2.4 Generate files ================== -Once you have written `configure.in', `Makefile.am', `acconfig.h', and -possibly `acinclude.m4', you must use autoconf and automake programs to +Once you have written 'configure.in', 'Makefile.am', 'acconfig.h', and +possibly 'acinclude.m4', you must use autoconf and automake programs to produce the first versions of the generated files. This is done by executing the following sequence of commands. @@ -580,34 +567,34 @@ executing the following sequence of commands. autoheader automake - The `aclocal' and `automake' commands are part of the automake -package, and the `autoconf' and `autoheader' commands are part of the + The 'aclocal' and 'automake' commands are part of the automake +package, and the 'autoconf' and 'autoheader' commands are part of the autoconf package. - If you are using a `m4' subdirectory for your macros, you will need -to use the `-I m4' option when you run `aclocal'. + If you are using a 'm4' subdirectory for your macros, you will need +to use the '-I m4' option when you run 'aclocal'. - If you are not using the Cygnus tree, use the `-a' option when -running `automake' command in order to copy the required support files + If you are not using the Cygnus tree, use the '-a' option when +running 'automake' command in order to copy the required support files into your source directory. If you are using libtool, you must build and install the libtool -package with the same `--prefix' and `--exec-prefix' options as you -used with the autoconf and automake packages. You must do this before +package with the same '--prefix' and '--exec-prefix' options as you used +with the autoconf and automake packages. You must do this before running any of the above commands. If you are not using the Cygnus -tree, you will need to run the `libtoolize' program to copy the libtool +tree, you will need to run the 'libtoolize' program to copy the libtool support files into your directory. Once you have managed to run these commands without getting any -errors, you should create a new empty directory, and run the `configure' -script which will have been created by `autoconf' with the -`--enable-maintainer-mode' option. This will give you a set of +errors, you should create a new empty directory, and run the 'configure' +script which will have been created by 'autoconf' with the +'--enable-maintainer-mode' option. This will give you a set of Makefiles which will include rules to automatically rebuild all the generated files. After doing that, whenever you have changed some of the input files -and want to regenerated the other files, go to your object directory -and run `make'. Doing this is more reliable than trying to rebuild the +and want to regenerated the other files, go to your object directory and +run 'make'. Doing this is more reliable than trying to rebuild the files manually, because there are complex order dependencies and it is easy to forget something. @@ -619,9 +606,9 @@ File: configure.info, Node: Getting Started Example, Prev: Generate files, Up Let's consider a trivial example. - Suppose we want to write a simple version of `touch'. Our program, -which we will call `poke', will take a single file name argument, and -use the `utime' system call to set the modification and access times of + Suppose we want to write a simple version of 'touch'. Our program, +which we will call 'poke', will take a single file name argument, and +use the 'utime' system call to set the modification and access times of the file to the current time. We want this program to be highly portable. @@ -641,7 +628,7 @@ File: configure.info, Node: Getting Started Example 1, Next: Getting Started E 2.5.1 First Try --------------- -Here is our first try at `poke.c'. Note that we've written it without +Here is our first try at 'poke.c'. Note that we've written it without ANSI/ISO C prototypes, since we want it to be highly portable. #include <stdio.h> @@ -669,7 +656,7 @@ ANSI/ISO C prototypes, since we want it to be highly portable. exit (0); } - We also write a simple `Makefile'. + We also write a simple 'Makefile'. CC = gcc CFLAGS = -g -O2 @@ -683,24 +670,24 @@ ANSI/ISO C prototypes, since we want it to be highly portable. Unfortunately, there are a few problems. - On older Unix systems derived from BSD 4.3, the `utime' system call -does not accept a second argument of `NULL'. On those systems, we need -to pass a pointer to `struct utimbuf' structure. Unfortunately, even + On older Unix systems derived from BSD 4.3, the 'utime' system call +does not accept a second argument of 'NULL'. On those systems, we need +to pass a pointer to 'struct utimbuf' structure. Unfortunately, even older systems don't define that structure; on those systems, we need to -pass an array of two `long' values. +pass an array of two 'long' values. - The header file `stdlib.h' was invented by ANSI C, and older systems -don't have a copy. We included it above to get a declaration of `exit'. + The header file 'stdlib.h' was invented by ANSI C, and older systems +don't have a copy. We included it above to get a declaration of 'exit'. - We can find some of these portability problems by running -`autoscan', which will create a `configure.scan' file which we can use -as a prototype for our `configure.in' file. I won't show the output, -but it will notice the potential problems with `utime' and `stdlib.h'. + We can find some of these portability problems by running 'autoscan', +which will create a 'configure.scan' file which we can use as a +prototype for our 'configure.in' file. I won't show the output, but it +will notice the potential problems with 'utime' and 'stdlib.h'. - In our `Makefile', we don't provide any way to install the program. + In our 'Makefile', we don't provide any way to install the program. This doesn't matter much for such a simple example, but a real program -will need an `install' target. For that matter, we will also want a -`clean' target. +will need an 'install' target. For that matter, we will also want a +'clean' target. File: configure.info, Node: Getting Started Example 2, Next: Getting Started Example 3, Prev: Getting Started Example 1, Up: Getting Started Example @@ -710,7 +697,7 @@ File: configure.info, Node: Getting Started Example 2, Next: Getting Started E Here is our second try at this program. - We modify `poke.c' to use preprocessor macros to control what + We modify 'poke.c' to use preprocessor macros to control what features are available. (I've cheated a bit by using the same macro names which autoconf will use). @@ -774,8 +761,8 @@ names which autoconf will use). exit (0); } - Here is the associated `Makefile'. We've added support for the -preprocessor flags we use. We've also added `install' and `clean' + Here is the associated 'Makefile'. We've added support for the +preprocessor flags we use. We've also added 'install' and 'clean' targets. # Set this to your installation directory. @@ -814,18 +801,18 @@ targets. Some problems with this approach should be clear. - Users who want to compile poke will have to know how `utime' works -on their systems, so that they can uncomment the `Makefile' correctly. + Users who want to compile poke will have to know how 'utime' works on +their systems, so that they can uncomment the 'Makefile' correctly. - The installation is done using `cp', but many systems have an -`install' program which may be used, and which supports optional + The installation is done using 'cp', but many systems have an +'install' program which may be used, and which supports optional features such as stripping debugging information out of the installed binary. - The use of `Makefile' variables like `CC', `CFLAGS' and `LDFLAGS' + The use of 'Makefile' variables like 'CC', 'CFLAGS' and 'LDFLAGS' follows the requirements of the GNU standards. This is convenient for -all packages, since it reduces surprises for users. However, it is -easy to get the details wrong, and wind up with a slightly nonstandard +all packages, since it reduces surprises for users. However, it is easy +to get the details wrong, and wind up with a slightly nonstandard distribution. @@ -834,16 +821,16 @@ File: configure.info, Node: Getting Started Example 3, Next: Generate Files in 2.5.3 Third Try --------------- -For our third try at this program, we will write a `configure.in' -script to discover the configuration features on the host system, rather -than requiring the user to edit the `Makefile'. We will also write a -`Makefile.am' rather than a `Makefile'. +For our third try at this program, we will write a 'configure.in' script +to discover the configuration features on the host system, rather than +requiring the user to edit the 'Makefile'. We will also write a +'Makefile.am' rather than a 'Makefile'. - The only change to `poke.c' is to add a line at the start of the + The only change to 'poke.c' is to add a line at the start of the file: #include "config.h" - The new `configure.in' file is as follows. + The new 'configure.in' file is as follows. AC_INIT(poke.c) AM_INIT_AUTOMAKE(poke, 1.0) @@ -857,41 +844,38 @@ file: The first four macros in this file, and the last one, were described above; see *note Write configure.in::. If we omit these macros, then -when we run `automake' we will get a reminder that we need them. +when we run 'automake' we will get a reminder that we need them. The other macros are standard autoconf macros. -`AC_HEADER_STDC' +'AC_HEADER_STDC' Check for standard C headers. - -`AC_CHECK_HEADERS' +'AC_CHECK_HEADERS' Check whether a particular header file exists. - -`AC_EGREP_HEADER' +'AC_EGREP_HEADER' Check for a particular string in a particular header file, in this - case checking for `utimbuf' in `utime.h'. - -`AC_FUNC_UTIME_NULL' - Check whether `utime' accepts a NULL second argument to set the + case checking for 'utimbuf' in 'utime.h'. +'AC_FUNC_UTIME_NULL' + Check whether 'utime' accepts a NULL second argument to set the file change time to the current time. See the autoconf manual for a more complete description. - The new `Makefile.am' file is as follows. Note how simple this is -compared to our earlier `Makefile'. + The new 'Makefile.am' file is as follows. Note how simple this is +compared to our earlier 'Makefile'. bin_PROGRAMS = poke poke_SOURCES = poke.c - This means that we should build a single program name `poke'. It -should be installed in the binary directory, which we called `bindir' -earlier. The program `poke' is built from the source file `poke.c'. + This means that we should build a single program name 'poke'. It +should be installed in the binary directory, which we called 'bindir' +earlier. The program 'poke' is built from the source file 'poke.c'. - We must also write a `acconfig.h' file. Besides `PACKAGE' and -`VERSION', which must be mentioned for all packages which use automake, -we must include `HAVE_STRUCT_UTIMBUF', since we mentioned it in an -`AC_DEFINE'. + We must also write a 'acconfig.h' file. Besides 'PACKAGE' and +'VERSION', which must be mentioned for all packages which use automake, +we must include 'HAVE_STRUCT_UTIMBUF', since we mentioned it in an +'AC_DEFINE'. /* Name of package. */ #undef PACKAGE @@ -915,31 +899,27 @@ We must now generate the other files, using the following commands. autoheader automake - When we run `autoheader', it will remind us of any macros we forgot -to add to `acconfig.h'. + When we run 'autoheader', it will remind us of any macros we forgot +to add to 'acconfig.h'. - When we run `automake', it will want to add some files to our + When we run 'automake', it will want to add some files to our distribution. It will add them automatically if we use the -`--add-missing' option. +'--add-missing' option. - By default, `automake' will run in GNU mode, which means that it -will want us to create certain additional files; as of this writing, it -will want `NEWS', `README', `AUTHORS', and `ChangeLog', all of which -are files which should appear in a standard GNU distribution. We can -either add those files, or run `automake' with the `--foreign' option. + By default, 'automake' will run in GNU mode, which means that it will +want us to create certain additional files; as of this writing, it will +want 'NEWS', 'README', 'AUTHORS', and 'ChangeLog', all of which are +files which should appear in a standard GNU distribution. We can either +add those files, or run 'automake' with the '--foreign' option. Running these tools will generate the following files, all of which are described in the next chapter. - * `aclocal.m4' - - * `configure' - - * `config.in' - - * `Makefile.in' - - * `stamp-h.in' + * 'aclocal.m4' + * 'configure' + * 'config.in' + * 'Makefile.in' + * 'stamp-h.in' File: configure.info, Node: Files, Next: Configuration Names, Prev: Getting Started, Up: Top @@ -985,8 +965,8 @@ File: configure.info, Node: Developer Files Picture, Next: Written Developer F Here is a picture of the files which are written by the developer, the generated files which would be included with a complete source distribution, and the tools which create those files. The file names -are plain text and the tool names are enclosed by `*' characters (e.g., -`autoheader' is the name of a tool, not the name of a file). +are plain text and the tool names are enclosed by '*' characters (e.g., +'autoheader' is the name of a tool, not the name of a file). acconfig.h configure.in Makefile.am | | | @@ -994,9 +974,9 @@ are plain text and the tool names are enclosed by `*' characters (e.g., | | | | | v v | acinclude.m4 | | *autoheader* | | v v - | | v --->*automake* - v |--->*aclocal* | | - config.in | | | v + | | v --->*automake* + v |--->*aclocal* | | + config.in | | | v | v | Makefile.in | aclocal.m4--- | | @@ -1005,7 +985,6 @@ are plain text and the tool names are enclosed by `*' characters (e.g., | v configure - File: configure.info, Node: Written Developer Files, Next: Generated Developer Files, Prev: Developer Files Picture, Up: Developer Files @@ -1014,50 +993,50 @@ File: configure.info, Node: Written Developer Files, Next: Generated Developer The following files would be written by the developer. -`configure.in' - This is the configuration script. This script contains - invocations of autoconf macros. It may also contain ordinary - shell script code. This file will contain feature tests for - portability issues. The last thing in the file will normally be - an `AC_OUTPUT' macro listing which files to create when the - builder runs the configure script. This file is always required - when using the GNU configure system. *Note Write configure.in::. +'configure.in' + This is the configuration script. This script contains invocations + of autoconf macros. It may also contain ordinary shell script + code. This file will contain feature tests for portability issues. + The last thing in the file will normally be an 'AC_OUTPUT' macro + listing which files to create when the builder runs the configure + script. This file is always required when using the GNU configure + system. *Note Write configure.in::. -`Makefile.am' +'Makefile.am' This is the automake input file. It describes how the code should be built. It consists of definitions of automake variables. It may also contain ordinary Makefile targets. This file is only needed when using automake (newer tools normally use automake, but - there are still older tools which have not been converted, in - which the developer writes `Makefile.in' directly). *Note Write + there are still older tools which have not been converted, in which + the developer writes 'Makefile.in' directly). *Note Write Makefile.am::. -`acconfig.h' +'acconfig.h' When the configure script creates a portability header file, by - using `AM_CONFIG_HEADER' (or, if not using automake, - `AC_CONFIG_HEADER'), this file is used to describe macros which are - not recognized by the `autoheader' command. This is normally a - fairly uninteresting file, consisting of a collection of `#undef' - lines with comments. Normally any call to `AC_DEFINE' in - `configure.in' will require a line in this file. *Note Write + using 'AM_CONFIG_HEADER' (or, if not using automake, + 'AC_CONFIG_HEADER'), this file is used to describe macros which are + not recognized by the 'autoheader' command. This is normally a + fairly uninteresting file, consisting of a collection of '#undef' + lines with comments. Normally any call to 'AC_DEFINE' in + 'configure.in' will require a line in this file. *Note Write acconfig.h::. -`acinclude.m4' +'acinclude.m4' This file is not always required. It defines local autoconf - macros. These macros may then be used in `configure.in'. If you - don't need any local autoconf macros, then you don't need this - file at all. In fact, in general, you never need local autoconf - macros, since you can put everything in `configure.in', but - sometimes a local macro is convenient. - - Newer tools may omit `acinclude.m4', and instead use a - subdirectory, typically named `m4', and define `ACLOCAL_AMFLAGS = - -I m4' in `Makefile.am' to force `aclocal' to look there for macro + macros. These macros may then be used in 'configure.in'. If you + don't need any local autoconf macros, then you don't need this file + at all. In fact, in general, you never need local autoconf macros, + since you can put everything in 'configure.in', but sometimes a + local macro is convenient. + + Newer tools may omit 'acinclude.m4', and instead use a + subdirectory, typically named 'm4', and define 'ACLOCAL_AMFLAGS = + -I m4' in 'Makefile.am' to force 'aclocal' to look there for macro definitions. The macro definitions are then placed in separate files in that directory. - The `acinclude.m4' file is only used when using automake; in older - tools, the developer writes `aclocal.m4' directly, if it is needed. + The 'acinclude.m4' file is only used when using automake; in older + tools, the developer writes 'aclocal.m4' directly, if it is needed. File: configure.info, Node: Generated Developer Files, Prev: Written Developer Files, Up: Developer Files @@ -1068,59 +1047,59 @@ File: configure.info, Node: Generated Developer Files, Prev: Written Developer The following files would be generated by the developer. When using automake, these files are normally not generated manually -after the first time. Instead, the generated `Makefile' contains rules +after the first time. Instead, the generated 'Makefile' contains rules to automatically rebuild the files as required. When -`AM_MAINTAINER_MODE' is used in `configure.in' (the normal case in -Cygnus code), the automatic rebuilding rules will only be defined if -you configure using the `--enable-maintainer-mode' option. +'AM_MAINTAINER_MODE' is used in 'configure.in' (the normal case in +Cygnus code), the automatic rebuilding rules will only be defined if you +configure using the '--enable-maintainer-mode' option. When using automatic rebuilding, it is important to ensure that all -the various tools have been built and installed on your `PATH'. Using +the various tools have been built and installed on your 'PATH'. Using automatic rebuilding is highly recommended, so much so that I'm not going to explain what you have to do if you don't use it. -`configure' +'configure' This is the configure script which will be run when building the - package. This is generated by `autoconf' from `configure.in' and - `aclocal.m4'. This is a shell script. + package. This is generated by 'autoconf' from 'configure.in' and + 'aclocal.m4'. This is a shell script. -`Makefile.in' +'Makefile.in' This is the file which the configure script will turn into the - `Makefile' at build time. This file is generated by `automake' - from `Makefile.am'. If you aren't using automake, you must write - this file yourself. This file is pretty much a normal `Makefile', + 'Makefile' at build time. This file is generated by 'automake' + from 'Makefile.am'. If you aren't using automake, you must write + this file yourself. This file is pretty much a normal 'Makefile', with some configure substitutions for certain variables. -`aclocal.m4' - This file is created by the `aclocal' program, based on the - contents of `configure.in' and `acinclude.m4' (or, as noted in the - description of `acinclude.m4' above, on the contents of an `m4' +'aclocal.m4' + This file is created by the 'aclocal' program, based on the + contents of 'configure.in' and 'acinclude.m4' (or, as noted in the + description of 'acinclude.m4' above, on the contents of an 'm4' subdirectory). This file contains definitions of autoconf macros - which `autoconf' will use when generating the file `configure'. - These autoconf macros may be defined by you in `acinclude.m4' or + which 'autoconf' will use when generating the file 'configure'. + These autoconf macros may be defined by you in 'acinclude.m4' or they may be defined by other packages such as automake, libtool or gettext. If you aren't using automake, you will normally write - this file yourself; in that case, if `configure.in' uses only + this file yourself; in that case, if 'configure.in' uses only standard autoconf macros, this file will not be needed at all. -`config.in' - This file is created by `autoheader' based on `acconfig.h' and - `configure.in'. At build time, the configure script will define - some of the macros in it to create `config.h', which may then be +'config.in' + This file is created by 'autoheader' based on 'acconfig.h' and + 'configure.in'. At build time, the configure script will define + some of the macros in it to create 'config.h', which may then be included by your program. This permits your C code to use preprocessor conditionals to change its behaviour based on the characteristics of the host system. This file may also be called - `config.h.in'. + 'config.h.in'. -`stamp.h-in' +'stamp.h-in' This rather uninteresting file, which I omitted from the picture, - is generated by `automake'. It always contains the string - `timestamp'. It is used as a timestamp file indicating whether - `config.in' is up to date. Using a timestamp file means that - `config.in' can be marked as up to date without actually changing - its modification time. This is useful since `config.in' depends - upon `configure.in', but it is easy to change `configure.in' in a - way which does not affect `config.in'. + is generated by 'automake'. It always contains the string + 'timestamp'. It is used as a timestamp file indicating whether + 'config.in' is up to date. Using a timestamp file means that + 'config.in' can be marked as up to date without actually changing + its modification time. This is useful since 'config.in' depends + upon 'configure.in', but it is easy to change 'configure.in' in a + way which does not affect 'config.in'. File: configure.info, Node: Build Files, Next: Support Files, Prev: Developer Files, Up: Files @@ -1149,7 +1128,7 @@ File: configure.info, Node: Build Files Picture, Next: Build Files Description ------------------------- Here is a picture of the files which will be created at build time. -`config.status' is both a created file and a shell script which is run +'config.status' is both a created file and a shell script which is run to create other files, and the picture attempts to show that. config.in *configure* Makefile.in @@ -1161,7 +1140,6 @@ to create other files, and the picture attempts to show that. | | v v config.h Makefile - File: configure.info, Node: Build Files Description, Prev: Build Files Picture, Up: Build Files @@ -1170,44 +1148,43 @@ File: configure.info, Node: Build Files Description, Prev: Build Files Picture This is a description of the files which are created at build time. -`config.status' - The first step in building a package is to run the `configure' - script. The `configure' script will create the file - `config.status', which is itself a shell script. When you first - run `configure', it will automatically run `config.status'. An - `Makefile' derived from an automake generated `Makefile.in' will - contain rules to automatically run `config.status' again when +'config.status' + The first step in building a package is to run the 'configure' + script. The 'configure' script will create the file + 'config.status', which is itself a shell script. When you first + run 'configure', it will automatically run 'config.status'. An + 'Makefile' derived from an automake generated 'Makefile.in' will + contain rules to automatically run 'config.status' again when necessary to recreate certain files if their inputs change. -`Makefile' +'Makefile' This is the file which make will read to build the program. The - `config.status' script will transform `Makefile.in' into - `Makefile'. + 'config.status' script will transform 'Makefile.in' into + 'Makefile'. -`config.h' +'config.h' This file defines C preprocessor macros which C code can use to - adjust its behaviour on different systems. The `config.status' - script will transform `config.in' into `config.h'. + adjust its behaviour on different systems. The 'config.status' + script will transform 'config.in' into 'config.h'. -`config.cache' +'config.cache' This file did not fit neatly into the picture, and I omitted it. - It is used by the `configure' script to cache results between - runs. This can be an important speedup. If you modify - `configure.in' in such a way that the results of old tests should - change (perhaps you have added a new library to `LDFLAGS'), then - you will have to remove `config.cache' to force the tests to be - rerun. + It is used by the 'configure' script to cache results between runs. + This can be an important speedup. If you modify 'configure.in' in + such a way that the results of old tests should change (perhaps you + have added a new library to 'LDFLAGS'), then you will have to + remove 'config.cache' to force the tests to be rerun. The autoconf manual explains how to set up a site specific cache - file. This can speed up running `configure' scripts on your + file. This can speed up running 'configure' scripts on your system. -`stamp.h' +'stamp.h' This file, which I omitted from the picture, is similar to - `stamp-h.in'. It is used as a timestamp file indicating whether - `config.h' is up to date. This is useful since `config.h' depends - upon `config.status', but it is easy for `config.status' to change - in a way which does not affect `config.h'. + 'stamp-h.in'. It is used as a timestamp file indicating whether + 'config.h' is up to date. This is useful since 'config.h' depends + upon 'config.status', but it is easy for 'config.status' to change + in a way which does not affect 'config.h'. File: configure.info, Node: Support Files, Prev: Build Files, Up: Files @@ -1219,75 +1196,62 @@ The GNU configure and build system requires several support files to be included with your distribution. You do not normally need to concern yourself with these. If you are using the Cygnus tree, most are already present. Otherwise, they will be installed with your source by -`automake' (with the `--add-missing' option) and `libtoolize'. +'automake' (with the '--add-missing' option) and 'libtoolize'. You don't have to put the support files in the top level directory. -You can put them in a subdirectory, and use the `AC_CONFIG_AUX_DIR' -macro in `configure.in' to tell `automake' and the `configure' script +You can put them in a subdirectory, and use the 'AC_CONFIG_AUX_DIR' +macro in 'configure.in' to tell 'automake' and the 'configure' script where they are. In this section, I describe the support files, so that you can know what they are and why they are there. -`ABOUT-NLS' +'ABOUT-NLS' Added by automake if you are using gettext. This is a documentation file about the gettext project. - -`ansi2knr.c' - Used by an automake generated `Makefile' if you put `ansi2knr' in - `AUTOMAKE_OPTIONS' in `Makefile.am'. This permits compiling ANSI - C code with a K&R C compiler. - -`ansi2knr.1' - The man page which goes with `ansi2knr.c'. - -`config.guess' +'ansi2knr.c' + Used by an automake generated 'Makefile' if you put 'ansi2knr' in + 'AUTOMAKE_OPTIONS' in 'Makefile.am'. This permits compiling ANSI C + code with a K&R C compiler. +'ansi2knr.1' + The man page which goes with 'ansi2knr.c'. +'config.guess' A shell script which determines the configuration name for the system on which it is run. - -`config.sub' +'config.sub' A shell script which canonicalizes a configuration name entered by a user. - -`elisp-comp' +'elisp-comp' Used to compile Emacs LISP files. - -`install-sh' +'install-sh' A shell script which installs a program. This is used if the configure script can not find an install binary. - -`ltconfig' +'ltconfig' Used by libtool. This is a shell script which configures libtool for the particular system on which it is used. - -`ltmain.sh' +'ltmain.sh' Used by libtool. This is the actual libtool script which is used, - after it is configured by `ltconfig' to build a library. - -`mdate-sh' - A shell script used by an automake generated `Makefile' to pretty + after it is configured by 'ltconfig' to build a library. +'mdate-sh' + A shell script used by an automake generated 'Makefile' to pretty print the modification time of a file. This is used to maintain version numbers for texinfo files. - -`missing' - A shell script used if some tool is missing entirely. This is - used by an automake generated `Makefile' to avoid certain sorts of +'missing' + A shell script used if some tool is missing entirely. This is used + by an automake generated 'Makefile' to avoid certain sorts of timestamp problems. - -`mkinstalldirs' +'mkinstalldirs' A shell script which creates a directory, including all parent - directories. This is used by an automake generated `Makefile' + directories. This is used by an automake generated 'Makefile' during installation. - -`texinfo.tex' +'texinfo.tex' Required if you have any texinfo files. This is used when - converting Texinfo files into DVI using `texi2dvi' and TeX. - -`ylwrap' - A shell script used by an automake generated `Makefile' to run - programs like `bison', `yacc', `flex', and `lex'. These programs + converting Texinfo files into DVI using 'texi2dvi' and TeX. +'ylwrap' + A shell script used by an automake generated 'Makefile' to run + programs like 'bison', 'yacc', 'flex', and 'lex'. These programs default to producing output files with a fixed name, and the - `ylwrap' script runs them in a subdirectory to avoid file name + 'ylwrap' script runs them in a subdirectory to avoid file name conflicts when using a parallel make program. @@ -1296,10 +1260,9 @@ File: configure.info, Node: Configuration Names, Next: Cross Compilation Tools 4 Configuration Names ********************* -The GNU configure system names all systems using a "configuration -name". All such names used to be triplets (they may now contain four -parts in certain cases), and the term "configuration triplet" is still -seen. +The GNU configure system names all systems using a "configuration name". +All such names used to be triplets (they may now contain four parts in +certain cases), and the term "configuration triplet" is still seen. * Menu: @@ -1312,49 +1275,46 @@ File: configure.info, Node: Configuration Name Definition, Next: Using Configu 4.1 Configuration Name Definition ================================= -This is a string of the form CPU-MANUFACTURER-OPERATING_SYSTEM. In -some cases, this is extended to a four part form: +This is a string of the form CPU-MANUFACTURER-OPERATING_SYSTEM. In some +cases, this is extended to a four part form: CPU-MANUFACTURER-KERNEL-OPERATING_SYSTEM. When using a configuration name in a configure option, it is normally not necessary to specify an entire name. In particular, the MANUFACTURER field is often omitted, leading to strings such as -`i386-linux' or `sparc-sunos'. The shell script `config.sub' will +'i386-linux' or 'sparc-sunos'. The shell script 'config.sub' will translate these shortened strings into the canonical form. autoconf -will arrange for `config.sub' to be run automatically when it is needed. +will arrange for 'config.sub' to be run automatically when it is needed. The fields of a configuration name are as follows: CPU - The type of processor. This is typically something like `i386' or - `sparc'. More specific variants are used as well, such as - `mipsel' to indicate a little endian MIPS processor. - + The type of processor. This is typically something like 'i386' or + 'sparc'. More specific variants are used as well, such as 'mipsel' + to indicate a little endian MIPS processor. MANUFACTURER A somewhat freeform field which indicates the manufacturer of the - system. This is often simply `unknown'. Other common strings are - `pc' for an IBM PC compatible system, or the name of a workstation - vendor, such as `sun'. - + system. This is often simply 'unknown'. Other common strings are + 'pc' for an IBM PC compatible system, or the name of a workstation + vendor, such as 'sun'. OPERATING_SYSTEM The name of the operating system which is run on the system. This - will be something like `solaris2.5' or `irix6.3'. There is no + will be something like 'solaris2.5' or 'irix6.3'. There is no particular restriction on the version number, and strings like - `aix4.1.4.0' are seen. For an embedded system, which has no + 'aix4.1.4.0' are seen. For an embedded system, which has no operating system, this field normally indicates the type of object - file format, such as `elf' or `coff'. - + file format, such as 'elf' or 'coff'. KERNEL This is used mainly for GNU/Linux. A typical GNU/Linux - configuration name is `i586-pc-linux-gnulibc1'. In this case the - kernel, `linux', is separated from the operating system, - `gnulibc1'. + configuration name is 'i586-pc-linux-gnulibc1'. In this case the + kernel, 'linux', is separated from the operating system, + 'gnulibc1'. - The shell script `config.guess' will normally print the correct + The shell script 'config.guess' will normally print the correct configuration name for the system on which it is run. It does by -running `uname' and by examining other characteristics of the system. +running 'uname' and by examining other characteristics of the system. - Because `config.guess' can normally determine the configuration name + Because 'config.guess' can normally determine the configuration name for a machine, it is normally only necessary to specify a configuration name when building a cross-compiler or when building using a cross-compiler. @@ -1378,10 +1338,10 @@ name, you should define a macro which describes the feature, rather than defining a macro which describes the particular system you are on. Testing for a particular system is normally done using a case -statement in `configure.in'. The case statement might look something -like the following, assuming that `host' is a shell variable holding a -canonical configuration name (which will be the case if `configure.in' -uses the `AC_CANONICAL_HOST' or `AC_CANONICAL_SYSTEM' macro). +statement in 'configure.in'. The case statement might look something +like the following, assuming that 'host' is a shell variable holding a +canonical configuration name (which will be the case if 'configure.in' +uses the 'AC_CANONICAL_HOST' or 'AC_CANONICAL_SYSTEM' macro). case "${host}" in i[3-7]86-*-linux-gnu*) do something ;; @@ -1390,17 +1350,17 @@ uses the `AC_CANONICAL_HOST' or `AC_CANONICAL_SYSTEM' macro). mips*-*-elf*) do something ;; esac - It is particularly important to use `*' after the operating system + It is particularly important to use '*' after the operating system field, in order to match the version number which will be generated by -`config.guess'. +'config.guess'. In most cases you must be careful to match a range of processor -types. For most processor families, a trailing `*' suffices, as in -`mips*' above. For the i386 family, something along the lines of -`i[3-7]86' suffices at present. For the m68k family, you will need -something like `m68*'. Of course, if you do not need to match on the -processor, it is simpler to just replace the entire field by a `*', as -in `*-*-irix*'. +types. For most processor families, a trailing '*' suffices, as in +'mips*' above. For the i386 family, something along the lines of +'i[3-7]86' suffices at present. For the m68k family, you will need +something like 'm68*'. Of course, if you do not need to match on the +processor, it is simpler to just replace the entire field by a '*', as +in '*-*-irix*'. File: configure.info, Node: Cross Compilation Tools, Next: Canadian Cross, Prev: Configuration Names, Up: Top @@ -1428,8 +1388,8 @@ File: configure.info, Node: Cross Compilation Concepts, Next: Host and Target, ============================== A compiler which produces programs which run on a different system is a -cross compilation compiler, or simply a "cross compiler". Similarly, -we speak of cross assemblers, cross linkers, etc. +cross compilation compiler, or simply a "cross compiler". Similarly, we +speak of cross assemblers, cross linkers, etc. In the normal case, a compiler produces code which runs on the same system as the one on which the compiler runs. When it is necessary to @@ -1437,8 +1397,8 @@ distinguish this case from the cross compilation case, such a compiler is called a "native compiler". Similarly, we speak of native assemblers, etc. - Although the debugger is not strictly speaking a compilation tool, -it is nevertheless meaningful to speak of a cross debugger: a debugger + Although the debugger is not strictly speaking a compilation tool, it +is nevertheless meaningful to speak of a cross debugger: a debugger which is used to debug code which runs on another system. Everything that is said below about configuring cross compilation tools applies to the debugger as well. @@ -1462,14 +1422,14 @@ system. system and generates ELF programs for a MIPS embedded system. In this case the GNU/Linux system is the host, and the MIPS ELF system is the target. Such a compiler could be called a GNU/Linux cross MIPS ELF -compiler, or, equivalently, a `i386-linux-gnu' cross `mips-elf' +compiler, or, equivalently, a 'i386-linux-gnu' cross 'mips-elf' compiler. Naturally, most programs are not cross compilation tools. For those programs, it does not make sense to speak of a target. It only makes -sense to speak of a target for tools like `gcc' or the `binutils' which +sense to speak of a target for tools like 'gcc' or the 'binutils' which actually produce running code. For example, it does not make sense to -speak of the target of a tool like `bison' or `make'. +speak of the target of a tool like 'bison' or 'make'. Most cross compilation tools can also serve as native tools. For a native compilation tool, it is still meaningful to speak of a target. @@ -1484,33 +1444,31 @@ File: configure.info, Node: Using the Host Type, Next: Specifying the Target, ======================= In almost all cases the host system is the system on which you run the -`configure' script, and on which you build the tools (for the case when +'configure' script, and on which you build the tools (for the case when they differ, *note Canadian Cross::). If your configure script needs to know the configuration name of the host system, and the package is not a cross compilation tool and -therefore does not have a target, put `AC_CANONICAL_HOST' in -`configure.in'. This macro will arrange to define a few shell -variables when the `configure' script is run. +therefore does not have a target, put 'AC_CANONICAL_HOST' in +'configure.in'. This macro will arrange to define a few shell variables +when the 'configure' script is run. -`host' +'host' The canonical configuration name of the host. This will normally - be determined by running the `config.guess' shell script, although + be determined by running the 'config.guess' shell script, although the user is permitted to override this by using an explicit - `--host' option. - -`host_alias' - In the unusual case that the user used an explicit `--host' option, - this will be the argument to `--host'. In the normal case, this - will be the same as the `host' variable. - -`host_cpu' -`host_vendor' -`host_os' + '--host' option. +'host_alias' + In the unusual case that the user used an explicit '--host' option, + this will be the argument to '--host'. In the normal case, this + will be the same as the 'host' variable. +'host_cpu' +'host_vendor' +'host_os' The first three parts of the canonical configuration name. The shell variables may be used by putting shell code in -`configure.in'. For an example, see *note Using Configuration Names::. +'configure.in'. For an example, see *note Using Configuration Names::. File: configure.info, Node: Specifying the Target, Next: Using the Target Type, Prev: Using the Host Type, Up: Cross Compilation Tools @@ -1518,18 +1476,18 @@ File: configure.info, Node: Specifying the Target, Next: Using the Target Type 5.4 Specifying the Target ========================= -By default, the `configure' script will assume that the target is the +By default, the 'configure' script will assume that the target is the same as the host. This is the more common case; for example, it leads to a native compiler rather than a cross compiler. If you want to build a cross compilation tool, you must specify the -target explicitly by using the `--target' option when you run -`configure'. The argument to `--target' is the configuration name of +target explicitly by using the '--target' option when you run +'configure'. The argument to '--target' is the configuration name of the system for which you wish to generate code. *Note Configuration Names::. For example, to build tools which generate code for a MIPS ELF -embedded system, you would use `--target mips-elf'. +embedded system, you would use '--target mips-elf'. File: configure.info, Node: Using the Target Type, Next: Cross Tools in the Cygnus Tree, Prev: Specifying the Target, Up: Cross Compilation Tools @@ -1537,77 +1495,75 @@ File: configure.info, Node: Using the Target Type, Next: Cross Tools in the Cy 5.5 Using the Target Type ========================= -When writing `configure.in' for a cross compilation tool, you will need +When writing 'configure.in' for a cross compilation tool, you will need to use information about the target. To do this, put -`AC_CANONICAL_SYSTEM' in `configure.in'. +'AC_CANONICAL_SYSTEM' in 'configure.in'. - `AC_CANONICAL_SYSTEM' will look for a `--target' option and -canonicalize it using the `config.sub' shell script. It will also run -`AC_CANONICAL_HOST' (*note Using the Host Type::). + 'AC_CANONICAL_SYSTEM' will look for a '--target' option and +canonicalize it using the 'config.sub' shell script. It will also run +'AC_CANONICAL_HOST' (*note Using the Host Type::). The target type will be recorded in the following shell variables. Note that the host versions of these variables will also be defined by -`AC_CANONICAL_HOST'. +'AC_CANONICAL_HOST'. -`target' +'target' The canonical configuration name of the target. - -`target_alias' - The argument to the `--target' option. If the user did not specify - a `--target' option, this will be the same as `host_alias'. - -`target_cpu' -`target_vendor' -`target_os' +'target_alias' + The argument to the '--target' option. If the user did not specify + a '--target' option, this will be the same as 'host_alias'. +'target_cpu' +'target_vendor' +'target_os' The first three parts of the canonical target configuration name. - Note that if `host' and `target' are the same string, you can assume + Note that if 'host' and 'target' are the same string, you can assume a native configuration. If they are different, you can assume a cross configuration. - It is arguably possible for `host' and `target' to represent the -same system, but for the strings to not be identical. For example, if -`config.guess' returns `sparc-sun-sunos4.1.4', and somebody configures -with `--target sparc-sun-sunos4.1', then the slight differences between -the two versions of SunOS may be unimportant for your tool. However, -in the general case it can be quite difficult to determine whether the + It is arguably possible for 'host' and 'target' to represent the same +system, but for the strings to not be identical. For example, if +'config.guess' returns 'sparc-sun-sunos4.1.4', and somebody configures +with '--target sparc-sun-sunos4.1', then the slight differences between +the two versions of SunOS may be unimportant for your tool. However, in +the general case it can be quite difficult to determine whether the differences between two configuration names are significant or not. -Therefore, by convention, if the user specifies a `--target' option -without specifying a `--host' option, it is assumed that the user wants +Therefore, by convention, if the user specifies a '--target' option +without specifying a '--host' option, it is assumed that the user wants to configure a cross compilation tool. - The variables `target' and `target_alias' should be handled + The variables 'target' and 'target_alias' should be handled differently. In general, whenever the user may actually see a string, -`target_alias' should be used. This includes anything which may appear -in the file system, such as a directory name or part of a tool name. -It also includes any tool output, unless it is clearly labelled as the +'target_alias' should be used. This includes anything which may appear +in the file system, such as a directory name or part of a tool name. It +also includes any tool output, unless it is clearly labelled as the canonical target configuration name. This permits the user to use the -`--target' option to specify how the tool will appear to the outside +'--target' option to specify how the tool will appear to the outside world. On the other hand, when checking for characteristics of the target -system, `target' should be used. This is because a wide variety of -`--target' options may map into the same canonical configuration name. +system, 'target' should be used. This is because a wide variety of +'--target' options may map into the same canonical configuration name. You should not attempt to duplicate the canonicalization done by -`config.sub' in your own code. +'config.sub' in your own code. By convention, cross tools are installed with a prefix of the -argument used with the `--target' option, also known as `target_alias' +argument used with the '--target' option, also known as 'target_alias' (*note Using the Target Type::). If the user does not use the -`--target' option, and thus is building a native tool, no prefix is +'--target' option, and thus is building a native tool, no prefix is used. - For example, if gcc is configured with `--target mips-elf', then the -installed binary will be named `mips-elf-gcc'. If gcc is configured -without a `--target' option, then the installed binary will be named -`gcc'. + For example, if gcc is configured with '--target mips-elf', then the +installed binary will be named 'mips-elf-gcc'. If gcc is configured +without a '--target' option, then the installed binary will be named +'gcc'. - The autoconf macro `AC_ARG_PROGRAM' will handle this for you. If -you are using automake, no more need be done; the programs will + The autoconf macro 'AC_ARG_PROGRAM' will handle this for you. If you +are using automake, no more need be done; the programs will automatically be installed with the correct prefixes. Otherwise, see -the autoconf documentation for `AC_ARG_PROGRAM'. +the autoconf documentation for 'AC_ARG_PROGRAM'. File: configure.info, Node: Cross Tools in the Cygnus Tree, Prev: Using the Target Type, Up: Cross Compilation Tools @@ -1618,15 +1574,15 @@ File: configure.info, Node: Cross Tools in the Cygnus Tree, Prev: Using the Ta The Cygnus tree is used for various packages including gdb, the GNU binutils, and egcs. It is also, of course, used for Cygnus releases. - In the Cygnus tree, the top level `configure' script uses the old -Cygnus configure system, not autoconf. The top level `Makefile.in' is + In the Cygnus tree, the top level 'configure' script uses the old +Cygnus configure system, not autoconf. The top level 'Makefile.in' is written to build packages based on what is in the source tree, and -supports building a large number of tools in a single -`configure'/`make' step. +supports building a large number of tools in a single 'configure'/'make' +step. - The Cygnus tree may be configured with a `--target' option. The -`--target' option applies recursively to every subdirectory, and -permits building an entire set of cross tools at once. + The Cygnus tree may be configured with a '--target' option. The +'--target' option applies recursively to every subdirectory, and permits +building an entire set of cross tools at once. * Menu: @@ -1645,14 +1601,14 @@ The Cygnus tree distinguishes host libraries from target libraries. Host libraries are built with the compiler used to build the programs which run on the host, which is called the host compiler. This includes -libraries such as `bfd' and `tcl'. These libraries are built with the +libraries such as 'bfd' and 'tcl'. These libraries are built with the host compiler, and are linked into programs like the binutils or gcc which run on the host. Target libraries are built with the target compiler. If gcc is present in the source tree, then the target compiler is the gcc that is built using the host compiler. Target libraries are libraries such as -`newlib' and `libstdc++'. These libraries are not linked into the host +'newlib' and 'libstdc++'. These libraries are not linked into the host programs, but are instead made available for use with programs built with the target compiler. @@ -1662,17 +1618,17 @@ source tree, so that it will be used to build the target libraries. There is a complication here. The configure process needs to know which compiler you are going to use to build a tool; otherwise, the feature tests will not work correctly. The Cygnus tree handles this by -not configuring the target libraries until the target compiler is -built. In order to permit everything to build using a single -`configure'/`make', the configuration of the target libraries is +not configuring the target libraries until the target compiler is built. +In order to permit everything to build using a single +'configure'/'make', the configuration of the target libraries is actually triggered during the make step. - When the target libraries are configured, the `--target' option is -not used. Instead, the `--host' option is used with the argument of -the `--target' option for the overall configuration. If no `--target' -option was used for the overall configuration, the `--host' option will -be passed with the output of the `config.guess' shell script. Any -`--build' option is passed down unchanged. + When the target libraries are configured, the '--target' option is +not used. Instead, the '--host' option is used with the argument of the +'--target' option for the overall configuration. If no '--target' +option was used for the overall configuration, the '--host' option will +be passed with the output of the 'config.guess' shell script. Any +'--build' option is passed down unchanged. This translation of configuration options is done because since the target libraries are compiled with the target compiler, they are being @@ -1692,26 +1648,23 @@ used to build the target libraries. configuration. In a native configuration, the target libraries are normally configured and built as siblings of the host tools. In a cross configuration, the target libraries are normally built in a subdirectory -whose name is the argument to `--target'. This is mainly for -historical reasons. +whose name is the argument to '--target'. This is mainly for historical +reasons. - To summarize, running `configure' in the Cygnus tree configures all + To summarize, running 'configure' in the Cygnus tree configures all the host libraries and tools, but does not configure any of the target -libraries. Running `make' then does the following steps: +libraries. Running 'make' then does the following steps: * Build the host libraries. - - * Build the host programs, including gcc. Note that we call gcc - both a host program (since it runs on the host) and a target - compiler (since it generates code for the target). - + * Build the host programs, including gcc. Note that we call gcc both + a host program (since it runs on the host) and a target compiler + (since it generates code for the target). * Using the newly built target compiler, configure the target libraries. - * Build the target libraries. The steps need not be done in precisely this order, since they are -actually controlled by `Makefile' targets. +actually controlled by 'Makefile' targets. File: configure.info, Node: Target Library Configure Scripts, Next: Make Targets in Cygnus Tree, Prev: Host and Target Libraries, Up: Cross Tools in the Cygnus Tree @@ -1731,45 +1684,44 @@ exist when your target library is configured. This means that the configure script for a target library may not use any test which requires doing a link. This unfortunately includes many -useful autoconf macros, such as `AC_CHECK_FUNCS'. autoconf macros -which do a compile but not a link, such as `AC_CHECK_HEADERS', may be -used. +useful autoconf macros, such as 'AC_CHECK_FUNCS'. autoconf macros which +do a compile but not a link, such as 'AC_CHECK_HEADERS', may be used. This is a severe restriction, but normally not a fatal one, as target libraries can often assume the presence of other target libraries, and thus know which functions will be available. - As of this writing, the autoconf macro `AC_PROG_CC' does a link to + As of this writing, the autoconf macro 'AC_PROG_CC' does a link to make sure that the compiler works. This may fail in a target library, so target libraries must use a different set of macros to locate the -compiler. See the `configure.in' file in a directory like `libiberty' -or `libgloss' for an example. +compiler. See the 'configure.in' file in a directory like 'libiberty' +or 'libgloss' for an example. As noted in the previous section, target libraries are sometimes built in directories which are siblings to the host tools, and are -sometimes built in a subdirectory. The `--with-target-subdir' configure +sometimes built in a subdirectory. The '--with-target-subdir' configure option will be passed when the library is configured. Its value will be an empty string if the target library is a sibling. Its value will be the name of the subdirectory if the target library is in a subdirectory. If the overall build is not a native build (i.e., the overall -configure used the `--target' option), then the library will be -configured with the `--with-cross-host' option. The value of this +configure used the '--target' option), then the library will be +configured with the '--with-cross-host' option. The value of this option will be the host system of the overall build. Recall that the host system of the library will be the target of the overall build. If -the overall build is a native build, the `--with-cross-host' option -will not be used. +the overall build is a native build, the '--with-cross-host' option will +not be used. A library which can be built both standalone and as a target library may want to install itself into different directories depending upon the case. When built standalone, or when built native, the library should -be installed in `$(libdir)'. When built as a target library which is -not native, the library should be installed in `$(tooldir)/lib'. The -`--with-cross-host' option may be used to distinguish these cases. +be installed in '$(libdir)'. When built as a target library which is +not native, the library should be installed in '$(tooldir)/lib'. The +'--with-cross-host' option may be used to distinguish these cases. - This same test of `--with-cross-host' may be used to see whether it + This same test of '--with-cross-host' may be used to see whether it is OK to use link tests in the configure script. If the -`--with-cross-host' option is not used, then the library is being built +'--with-cross-host' option is not used, then the library is being built either standalone or native, and a link should work. @@ -1778,30 +1730,30 @@ File: configure.info, Node: Make Targets in Cygnus Tree, Next: Target libibert 5.6.3 Make Targets in Cygnus Tree --------------------------------- -The top level `Makefile' in the Cygnus tree defines targets for every +The top level 'Makefile' in the Cygnus tree defines targets for every known subdirectory. - For every subdirectory DIR which holds a host library or program, -the `Makefile' target `all-DIR' will build that library or program. + For every subdirectory DIR which holds a host library or program, the +'Makefile' target 'all-DIR' will build that library or program. There are dependencies among host tools. For example, building gcc requires first building gas, because the gcc build process invokes the target assembler. These dependencies are reflected in the top level -`Makefile'. +'Makefile'. For every subdirectory DIR which holds a target library, the -`Makefile' target `configure-target-DIR' will configure that library. -The `Makefile' target `all-target-DIR' will build that library. +'Makefile' target 'configure-target-DIR' will configure that library. +The 'Makefile' target 'all-target-DIR' will build that library. - Every `configure-target-DIR' target depends upon `all-gcc', since + Every 'configure-target-DIR' target depends upon 'all-gcc', since gcc, the target compiler, is required to configure the tool. Every -`all-target-DIR' target depends upon the corresponding -`configure-target-DIR' target. +'all-target-DIR' target depends upon the corresponding +'configure-target-DIR' target. There are several other targets which may be of interest for each -directory: `install-DIR', `clean-DIR', and `check-DIR'. There are also -corresponding `target' versions of these for the target libraries , -such as `install-target-DIR'. +directory: 'install-DIR', 'clean-DIR', and 'check-DIR'. There are also +corresponding 'target' versions of these for the target libraries , such +as 'install-target-DIR'. File: configure.info, Node: Target libiberty, Prev: Make Targets in Cygnus Tree, Up: Cross Tools in the Cygnus Tree @@ -1809,17 +1761,17 @@ File: configure.info, Node: Target libiberty, Prev: Make Targets in Cygnus Tre 5.6.4 Target libiberty ---------------------- -The `libiberty' subdirectory is currently a special case, in that it is -the only directory which is built both using the host compiler and -using the target compiler. +The 'libiberty' subdirectory is currently a special case, in that it is +the only directory which is built both using the host compiler and using +the target compiler. - This is because the files in `libiberty' are used when building the -host tools, and they are also incorporated into the `libstdc++' target + This is because the files in 'libiberty' are used when building the +host tools, and they are also incorporated into the 'libstdc++' target library as support code. This duality does not pose any particular difficulties. It means -that there are targets for both `all-libiberty' and -`all-target-libiberty'. +that there are targets for both 'all-libiberty' and +'all-target-libiberty'. In a native configuration, when target libraries are not built in a subdirectory, the same objects are normally used as both the host build @@ -1828,8 +1780,8 @@ only C code, and in a native configuration the results of the host compiler and the target compiler are normally interoperable. Irix 6 is again an exception here, since the SGI native compiler -defaults to using the `O32' ABI, and gcc defaults to using the `N32' -ABI. On Irix 6, the target libraries are built in a subdirectory even +defaults to using the 'O32' ABI, and gcc defaults to using the 'N32' +ABI. On Irix 6, the target libraries are built in a subdirectory even for a native configuration, avoiding this problem. There are currently no other libraries built for both the host and @@ -1880,9 +1832,9 @@ available for some reason; perhaps you actually don't have one, but you want to build the tools for somebody else to use. Or perhaps your GNU/Linux system is much faster than your Solaris system. - A Canadian Cross build is most frequently used when building -programs to run on a non-Unix system, such as DOS or Windows. It may -be simpler to configure and build on a Unix system than to support the + A Canadian Cross build is most frequently used when building programs +to run on a non-Unix system, such as DOS or Windows. It may be simpler +to configure and build on a Unix system than to support the configuration machinery on a non-Unix system. @@ -1947,37 +1899,37 @@ File: configure.info, Node: Build and Host Options, Next: CCross not in Cygnus 6.4 Build and Host Options ========================== -When you run `configure', you must use both the `--build' and `--host' +When you run 'configure', you must use both the '--build' and '--host' options. - The `--build' option is used to specify the configuration name of -the build system. This can normally be the result of running the -`config.guess' shell script, and it is reasonable to use -`--build=`config.guess`'. + The '--build' option is used to specify the configuration name of the +build system. This can normally be the result of running the +'config.guess' shell script, and it is reasonable to use +'--build=`config.guess`'. - The `--host' option is used to specify the configuration name of the + The '--host' option is used to specify the configuration name of the host system. - As we explained earlier, `config.guess' is used to set the default -value for the `--host' option (*note Using the Host Type::). We can -now see that since `config.guess' returns the type of system on which -it is run, it really identifies the build system. Since the host -system is normally the same as the build system (i.e., people do not -normally build using a cross compiler), it is reasonable to use the -result of `config.guess' as the default for the host system when the -`--host' option is not used. - - It might seem that if the `--host' option were used without the -`--build' option that the configure script could run `config.guess' to + As we explained earlier, 'config.guess' is used to set the default +value for the '--host' option (*note Using the Host Type::). We can now +see that since 'config.guess' returns the type of system on which it is +run, it really identifies the build system. Since the host system is +normally the same as the build system (i.e., people do not normally +build using a cross compiler), it is reasonable to use the result of +'config.guess' as the default for the host system when the '--host' +option is not used. + + It might seem that if the '--host' option were used without the +'--build' option that the configure script could run 'config.guess' to determine the build system, and presume a Canadian Cross if the result -of `config.guess' differed from the `--host' option. However, for +of 'config.guess' differed from the '--host' option. However, for historical reasons, some configure scripts are routinely run using an -explicit `--host' option, rather than using the default from -`config.guess'. As noted earlier, it is difficult or impossible to +explicit '--host' option, rather than using the default from +'config.guess'. As noted earlier, it is difficult or impossible to reliably compare configuration names (*note Using the Target Type::). -Therefore, by convention, if the `--host' option is used, but the -`--build' option is not used, then the build system defaults to the -host system. +Therefore, by convention, if the '--host' option is used, but the +'--build' option is not used, then the build system defaults to the host +system. File: configure.info, Node: CCross not in Cygnus Tree, Next: CCross in Cygnus Tree, Prev: Build and Host Options, Up: Canadian Cross @@ -1987,21 +1939,21 @@ File: configure.info, Node: CCross not in Cygnus Tree, Next: CCross in Cygnus If you are not using the Cygnus tree, you must explicitly specify the cross tools which you want to use to build the program. This is done by -setting environment variables before running the `configure' script. +setting environment variables before running the 'configure' script. - You must normally set at least the environment variables `CC', `AR', -and `RANLIB' to the cross tools which you want to use to build. + You must normally set at least the environment variables 'CC', 'AR', +and 'RANLIB' to the cross tools which you want to use to build. For some programs, you must set additional cross tools as well, such -as `AS', `LD', or `NM'. +as 'AS', 'LD', or 'NM'. You would set these environment variables to the build cross tools which you are going to use. For example, if you are building a Solaris program on a GNU/Linux system, and your GNU/Linux cross Solaris compiler were named -`solaris-gcc', then you would set the environment variable `CC' to -`solaris-gcc'. +'solaris-gcc', then you would set the environment variable 'CC' to +'solaris-gcc'. File: configure.info, Node: CCross in Cygnus Tree, Next: Supporting Canadian Cross, Prev: CCross not in Cygnus Tree, Up: Canadian Cross @@ -2024,26 +1976,26 @@ File: configure.info, Node: Standard Cygnus CCross, Next: Cross Cygnus CCross, ------------------------------- When configuring a Canadian Cross in the Cygnus tree, all the -appropriate environment variables are automatically set to `HOST-TOOL', -where HOST is the value used for the `--host' option, and TOOL is the -name of the tool (e.g., `gcc', `as', etc.). These tools must be on -your `PATH'. +appropriate environment variables are automatically set to 'HOST-TOOL', +where HOST is the value used for the '--host' option, and TOOL is the +name of the tool (e.g., 'gcc', 'as', etc.). These tools must be on your +'PATH'. Adding a prefix of HOST will give the usual name for the build cross host tools. To see this, consider that when these cross tools were built, they were configured to run on the build system and to produce code for the host system. That is, they were configured with a -`--target' option that is the same as the system which we are now +'--target' option that is the same as the system which we are now calling the host. Recall that the default name for installed cross tools uses the target system as a prefix (*note Using the Target Type::). Since that is the system which we are now calling the host, HOST is the right prefix to use. - For example, if you configure with `--build=i386-linux-gnu' and -`--host=solaris', then the Cygnus tree will automatically default to -using the compiler `solaris-gcc'. You must have previously built and -installed this compiler, probably by doing a build with no `--host' -option and with a `--target' option of `solaris'. + For example, if you configure with '--build=i386-linux-gnu' and +'--host=solaris', then the Cygnus tree will automatically default to +using the compiler 'solaris-gcc'. You must have previously built and +installed this compiler, probably by doing a build with no '--host' +option and with a '--target' option of 'solaris'. File: configure.info, Node: Cross Cygnus CCross, Prev: Standard Cygnus CCross, Up: CCross in Cygnus Tree @@ -2070,19 +2022,19 @@ be used when building the target libraries. For example, it would be possible to build just the host cross target tools on the build system, to copy the tools to the host system, and to build the target libraries on the host system. The requirement for -build cross target tools is imposed by the Cygnus tree, which expects -to be able to build both host programs and target libraries in a single -`configure'/`make' step. Because it builds these in a single step, it +build cross target tools is imposed by the Cygnus tree, which expects to +be able to build both host programs and target libraries in a single +'configure'/'make' step. Because it builds these in a single step, it expects to be able to build the target libraries on the build system, which means that it must use a build cross target toolchain. For example, suppose you want to build a Windows cross MIPS ELF -compiler on a GNU/Linux system. You must have previously installed -both a GNU/Linux cross Windows compiler and a GNU/Linux cross MIPS ELF +compiler on a GNU/Linux system. You must have previously installed both +a GNU/Linux cross Windows compiler and a GNU/Linux cross MIPS ELF compiler. - In order to build the Windows (configuration name `i386-cygwin32') -cross MIPS ELF (configure name `mips-elf') compiler, you might execute + In order to build the Windows (configuration name 'i386-cygwin32') +cross MIPS ELF (configure name 'mips-elf') compiler, you might execute the following commands (long command lines are broken across lines with a trailing backslash as a continuation character). @@ -2108,8 +2060,8 @@ a trailing backslash as a continuation character). make make install - You would then copy the contents of WININSTALLDIR over to the -Windows machine, and run the resulting programs. + You would then copy the contents of WININSTALLDIR over to the Windows +machine, and run the resulting programs. File: configure.info, Node: Supporting Canadian Cross, Prev: CCross in Cygnus Tree, Up: Canadian Cross @@ -2134,60 +2086,60 @@ File: configure.info, Node: CCross in Configure, Next: CCross in Make, Up: Su 6.7.1 Supporting Canadian Cross in Configure Scripts ---------------------------------------------------- -In a `configure.in' file, after calling `AC_PROG_CC', you can find out +In a 'configure.in' file, after calling 'AC_PROG_CC', you can find out whether this is a Canadian Cross configure by examining the shell -variable `cross_compiling'. In a Canadian Cross, which means that the -compiler is a cross compiler, `cross_compiling' will be `yes'. In a -normal configuration, `cross_compiling' will be `no'. +variable 'cross_compiling'. In a Canadian Cross, which means that the +compiler is a cross compiler, 'cross_compiling' will be 'yes'. In a +normal configuration, 'cross_compiling' will be 'no'. You ordinarily do not need to know the type of the build system in a configure script. However, if you do need that information, you can get -it by using the macro `AC_CANONICAL_SYSTEM', the same macro that is -used to determine the target system. This macro will set the variables -`build', `build_alias', `build_cpu', `build_vendor', and `build_os', -which correspond to the similar `target' and `host' variables, except +it by using the macro 'AC_CANONICAL_SYSTEM', the same macro that is used +to determine the target system. This macro will set the variables +'build', 'build_alias', 'build_cpu', 'build_vendor', and 'build_os', +which correspond to the similar 'target' and 'host' variables, except that they describe the build system. - When writing tests in `configure.in', you must remember that you -want to test the host environment, not the build environment. + When writing tests in 'configure.in', you must remember that you want +to test the host environment, not the build environment. - Macros like `AC_CHECK_FUNCS' which use the compiler will test the + Macros like 'AC_CHECK_FUNCS' which use the compiler will test the host environment. That is because the tests will be done by running the compiler, which is actually a build cross host compiler. If the compiler can find the function, that means that the function is present in the host environment. - Tests like `test -f /dev/ptyp0', on the other hand, will test the + Tests like 'test -f /dev/ptyp0', on the other hand, will test the build environment. Remember that the configure script is running on the build system, not the host system. If your configure scripts examines files, those files will be on the build system. Whatever you determine based on those files may or may not be the case on the host system. Most autoconf macros will work correctly for a Canadian Cross. The -main exception is `AC_TRY_RUN'. This macro tries to compile and run a +main exception is 'AC_TRY_RUN'. This macro tries to compile and run a test program. This will fail in a Canadian Cross, because the program will be compiled for the host system, which means that it will not run on the build system. - The `AC_TRY_RUN' macro provides an optional argument to tell the + The 'AC_TRY_RUN' macro provides an optional argument to tell the configure script what to do in a Canadian Cross. If that argument is -not present, you will get a warning when you run `autoconf': +not present, you will get a warning when you run 'autoconf': warning: AC_TRY_RUN called without default to allow cross compiling - This tells you that the resulting `configure' script will not work -with a Canadian Cross. +This tells you that the resulting 'configure' script will not work with +a Canadian Cross. In some cases while it may better to perform a test at configure time, it is also possible to perform the test at run time. In such a -case you can use the cross compiling argument to `AC_TRY_RUN' to tell +case you can use the cross compiling argument to 'AC_TRY_RUN' to tell your program that the test could not be performed at configure time. There are a few other autoconf macros which will not work correctly -with a Canadian Cross: a partial list is `AC_FUNC_GETPGRP', -`AC_FUNC_SETPGRP', `AC_FUNC_SETVBUF_REVERSED', and -`AC_SYS_RESTARTABLE_SYSCALLS'. The `AC_CHECK_SIZEOF' macro is -generally not very useful with a Canadian Cross; it permits an optional -argument indicating the default size, but there is no way to know what -the correct default should be. +with a Canadian Cross: a partial list is 'AC_FUNC_GETPGRP', +'AC_FUNC_SETPGRP', 'AC_FUNC_SETVBUF_REVERSED', and +'AC_SYS_RESTARTABLE_SYSCALLS'. The 'AC_CHECK_SIZEOF' macro is generally +not very useful with a Canadian Cross; it permits an optional argument +indicating the default size, but there is no way to know what the +correct default should be. File: configure.info, Node: CCross in Make, Prev: CCross in Configure, Up: Supporting Canadian Cross @@ -2195,32 +2147,32 @@ File: configure.info, Node: CCross in Make, Prev: CCross in Configure, Up: Su 6.7.2 Supporting Canadian Cross in Makefiles. --------------------------------------------- -The main Canadian Cross issue in a `Makefile' arises when you want to +The main Canadian Cross issue in a 'Makefile' arises when you want to use a subsidiary program to generate code or data which you will then include in your real program. - If you compile this subsidiary program using `$(CC)' in the usual -way, you will not be able to run it. This is because `$(CC)' will -build a program for the host system, but the program is being built on -the build system. + If you compile this subsidiary program using '$(CC)' in the usual +way, you will not be able to run it. This is because '$(CC)' will build +a program for the host system, but the program is being built on the +build system. You must instead use a compiler for the build system, rather than the -host system. In the Cygnus tree, this make variable `$(CC_FOR_BUILD)' +host system. In the Cygnus tree, this make variable '$(CC_FOR_BUILD)' will hold a compiler for the build system. - Note that you should not include `config.h' in a file you are -compiling with `$(CC_FOR_BUILD)'. The `configure' script will build -`config.h' with information for the host system. However, you are + Note that you should not include 'config.h' in a file you are +compiling with '$(CC_FOR_BUILD)'. The 'configure' script will build +'config.h' with information for the host system. However, you are compiling the file using a compiler for the build system (a native compiler). Subsidiary programs are normally simple filters which do no user interaction, and it is normally possible to write them in a highly -portable fashion so that the absence of `config.h' is not crucial. +portable fashion so that the absence of 'config.h' is not crucial. - The gcc `Makefile.in' shows a complex situation in which certain -files, such as `rtl.c', must be compiled into both subsidiary programs + The gcc 'Makefile.in' shows a complex situation in which certain +files, such as 'rtl.c', must be compiled into both subsidiary programs run on the build system and into the final program. This approach may be of interest for advanced build system hackers. Note that the build -system compiler is rather confusingly called `HOST_CC'. +system compiler is rather confusingly called 'HOST_CC'. File: configure.info, Node: Cygnus Configure, Next: Multilibs, Prev: Canadian Cross, Up: Top @@ -2251,98 +2203,98 @@ File: configure.info, Node: Cygnus Configure Basics, Next: Cygnus Configure in =========================== Cygnus configure does not use any generated files; there is no program -corresponding to `autoconf'. Instead, there is a single shell script -named `configure' which may be found at the top of the Cygnus tree. -This shell script was written by hand; it was not generated by -autoconf, and it is incorrect, and indeed harmful, to run `autoconf' in -the top level of a Cygnus tree. +corresponding to 'autoconf'. Instead, there is a single shell script +named 'configure' which may be found at the top of the Cygnus tree. +This shell script was written by hand; it was not generated by autoconf, +and it is incorrect, and indeed harmful, to run 'autoconf' in the top +level of a Cygnus tree. Cygnus configure works in a particular directory by examining the -file `configure.in' in that directory. That file is broken into four +file 'configure.in' in that directory. That file is broken into four separate shell scripts. - The first is the contents of `configure.in' up to a line that starts -with `# per-host:'. This is the common part. + The first is the contents of 'configure.in' up to a line that starts +with '# per-host:'. This is the common part. - The second is the rest of `configure.in' up to a line that starts -with `# per-target:'. This is the per host part. + The second is the rest of 'configure.in' up to a line that starts +with '# per-target:'. This is the per host part. - The third is the rest of `configure.in' up to a line that starts -with `# post-target:'. This is the per target part. + The third is the rest of 'configure.in' up to a line that starts with +'# post-target:'. This is the per target part. - The fourth is the remainder of `configure.in'. This is the post + The fourth is the remainder of 'configure.in'. This is the post target part. If any of these comment lines are missing, the corresponding shell script is empty. Cygnus configure will first execute the common part. This must set -the shell variable `srctrigger' to the name of a source file, to -confirm that Cygnus configure is looking at the right directory. This -may set the shell variables `package_makefile_frag' and -`package_makefile_rules_frag'. +the shell variable 'srctrigger' to the name of a source file, to confirm +that Cygnus configure is looking at the right directory. This may set +the shell variables 'package_makefile_frag' and +'package_makefile_rules_frag'. - Cygnus configure will next set the `build' and `host' shell + Cygnus configure will next set the 'build' and 'host' shell variables, and execute the per host part. This may set the shell -variable `host_makefile_frag'. +variable 'host_makefile_frag'. - Cygnus configure will next set the `target' variable, and execute -the per target part. This may set the shell variable -`target_makefile_frag'. + Cygnus configure will next set the 'target' variable, and execute the +per target part. This may set the shell variable +'target_makefile_frag'. - Any of these scripts may set the `subdirs' shell variable. This -variable is a list of subdirectories where a `Makefile.in' file may be -found. Cygnus configure will automatically look for a `Makefile.in' -file in the current directory. The `subdirs' shell variable is not + Any of these scripts may set the 'subdirs' shell variable. This +variable is a list of subdirectories where a 'Makefile.in' file may be +found. Cygnus configure will automatically look for a 'Makefile.in' +file in the current directory. The 'subdirs' shell variable is not normally used, and I believe that the only directory which uses it at -present is `newlib'. +present is 'newlib'. - For each `Makefile.in', Cygnus configure will automatically create a -`Makefile' by adding definitions for `make' variables such as `host' -and `target', and automatically editing the values of `make' variables -such as `prefix' if they are present. + For each 'Makefile.in', Cygnus configure will automatically create a +'Makefile' by adding definitions for 'make' variables such as 'host' and +'target', and automatically editing the values of 'make' variables such +as 'prefix' if they are present. - Also, if any of the `makefile_frag' shell variables are set, Cygnus + Also, if any of the 'makefile_frag' shell variables are set, Cygnus configure will interpret them as file names relative to either the working directory or the source directory, and will read the contents of -the file into the generated `Makefile'. The file contents will be read -in after the first line in `Makefile.in' which starts with `####'. +the file into the generated 'Makefile'. The file contents will be read +in after the first line in 'Makefile.in' which starts with '####'. - These `Makefile' fragments are used to customize behaviour for a + These 'Makefile' fragments are used to customize behaviour for a particular host or target. They serve to select particular files to compile, and to define particular preprocessor macros by providing -values for `make' variables which are then used during compilation. +values for 'make' variables which are then used during compilation. Cygnus configure, unlike autoconf, normally does not do feature tests, and normally requires support to be added manually for each new host. - The `Makefile' fragment support is similar to the autoconf -`AC_SUBST_FILE' macro. + The 'Makefile' fragment support is similar to the autoconf +'AC_SUBST_FILE' macro. - After creating each `Makefile', the post target script will be run + After creating each 'Makefile', the post target script will be run (i.e., it may be run several times). This script may further customize -the `Makefile'. When it is run, the shell variable `Makefile' will -hold the name of the `Makefile', including the appropriate directory +the 'Makefile'. When it is run, the shell variable 'Makefile' will hold +the name of the 'Makefile', including the appropriate directory component. - Like an autoconf generated `configure' script, Cygnus configure will -create a file named `config.status' which, when run, will automatically -recreate the configuration. The `config.status' file will simply + Like an autoconf generated 'configure' script, Cygnus configure will +create a file named 'config.status' which, when run, will automatically +recreate the configuration. The 'config.status' file will simply execute the Cygnus configure script again with the appropriate arguments. - Any of the parts of `configure.in' may set the shell variables -`files' and `links'. Cygnus configure will set up symlinks from the -names in `links' to the files named in `files'. This is similar to the -autoconf `AC_LINK_FILES' macro. + Any of the parts of 'configure.in' may set the shell variables +'files' and 'links'. Cygnus configure will set up symlinks from the +names in 'links' to the files named in 'files'. This is similar to the +autoconf 'AC_LINK_FILES' macro. - Finally, any of the parts of `configure.in' may set the shell -variable `configdirs' to a set of subdirectories. If it is set, Cygnus + Finally, any of the parts of 'configure.in' may set the shell +variable 'configdirs' to a set of subdirectories. If it is set, Cygnus configure will recursively run the configure process in each subdirectory. If the subdirectory uses Cygnus configure, it will -contain a `configure.in' file but no `configure' file, in which case +contain a 'configure.in' file but no 'configure' file, in which case Cygnus configure will invoke itself recursively. If the subdirectory -has a `configure' file, Cygnus configure assumes that it is an autoconf -generated `configure' script, and simply invokes it directly. +has a 'configure' file, Cygnus configure assumes that it is an autoconf +generated 'configure' script, and simply invokes it directly. File: configure.info, Node: Cygnus Configure in C++ Libraries, Prev: Cygnus Configure Basics, Up: Cygnus Configure @@ -2352,18 +2304,18 @@ File: configure.info, Node: Cygnus Configure in C++ Libraries, Prev: Cygnus Co The C++ library configure system, written by Per Bothner, deserves special mention. It uses Cygnus configure, but it does feature testing -like that done by autoconf generated `configure' scripts. This -approach is used in the libraries `libio', `libstdc++', and `libg++'. +like that done by autoconf generated 'configure' scripts. This approach +is used in the libraries 'libio', 'libstdc++', and 'libg++'. - Most of the `Makefile' information is written out by the shell -script `libio/config.shared'. Each `configure.in' file sets certain -shell variables, and then invokes `config.shared' to create two package -`Makefile' fragments. These fragments are then incorporated into the -resulting `Makefile' by the Cygnus configure script. + Most of the 'Makefile' information is written out by the shell script +'libio/config.shared'. Each 'configure.in' file sets certain shell +variables, and then invokes 'config.shared' to create two package +'Makefile' fragments. These fragments are then incorporated into the +resulting 'Makefile' by the Cygnus configure script. - The file `_G_config.h' is created in the `libio' object directory by -running the shell script `libio/gen-params'. This shell script uses -feature tests to define macros and typedefs in `_G_config.h'. + The file '_G_config.h' is created in the 'libio' object directory by +running the shell script 'libio/gen-params'. This shell script uses +feature tests to define macros and typedefs in '_G_config.h'. File: configure.info, Node: Multilibs, Next: FAQ, Prev: Cygnus Configure, Up: Top @@ -2372,20 +2324,20 @@ File: configure.info, Node: Multilibs, Next: FAQ, Prev: Cygnus Configure, Up *********** For some targets gcc may have different processor requirements depending -upon command line options. An obvious example is the `-msoft-float' +upon command line options. An obvious example is the '-msoft-float' option supported on several processors. This option means that the floating point registers are not available, which means that floating point operations must be done by calling an emulation subroutine rather than by using machine instructions. For such options, gcc is often configured to compile target libraries -twice: once with `-msoft-float' and once without. When gcc compiles +twice: once with '-msoft-float' and once without. When gcc compiles target libraries more than once, the resulting libraries are called "multilibs". Multilibs are not really part of the GNU configure and build system, -but we discuss them here since they require support in the `configure' -scripts and `Makefile's used for target libraries. +but we discuss them here since they require support in the 'configure' +scripts and 'Makefile's used for target libraries. * Menu: @@ -2398,20 +2350,20 @@ File: configure.info, Node: Multilibs in gcc, Next: Multilibs in Target Librar 8.1 Multilibs in gcc ==================== -In gcc, multilibs are defined by setting the variable -`MULTILIB_OPTIONS' in the target `Makefile' fragment. Several other -`MULTILIB' variables may also be defined there. *Note The Target -Makefile Fragment: (gcc)Target Fragment. +In gcc, multilibs are defined by setting the variable 'MULTILIB_OPTIONS' +in the target 'Makefile' fragment. Several other 'MULTILIB' variables +may also be defined there. *Note The Target Makefile Fragment: +(gcc)Target Fragment. If you have built gcc, you can see what multilibs it uses by running -it with the `-print-multi-lib' option. The output `.;' means that no +it with the '-print-multi-lib' option. The output '.;' means that no multilibs are used. In general, the output is a sequence of lines, one -per multilib. The first part of each line, up to the `;', is the name +per multilib. The first part of each line, up to the ';', is the name of the multilib directory. The second part is a list of compiler -options separated by `@' characters. +options separated by '@' characters. Multilibs are built in a tree of directories. The top of the tree, -represented by `.' in the list of multilib directories, is the default +represented by '.' in the list of multilib directories, is the default library to use when no special compiler options are used. The subdirectories of the tree hold versions of the library to use when particular compiler options are used. @@ -2425,90 +2377,86 @@ File: configure.info, Node: Multilibs in Target Libraries, Prev: Multilibs in The target libraries in the Cygnus tree are automatically built with multilibs. That means that each library is built multiple times. - This default is set in the top level `configure.in' file, by adding -`--enable-multilib' to the list of arguments passed to configure when -it is run for the target libraries (*note Host and Target Libraries::). + This default is set in the top level 'configure.in' file, by adding +'--enable-multilib' to the list of arguments passed to configure when it +is run for the target libraries (*note Host and Target Libraries::). - Each target library uses the shell script `config-ml.in', written by + Each target library uses the shell script 'config-ml.in', written by Doug Evans, to prepare to build target libraries. This shell script is -invoked after the `Makefile' has been created by the `configure' -script. If multilibs are not enabled, it does nothing, otherwise it -modifies the `Makefile' to support multilibs. +invoked after the 'Makefile' has been created by the 'configure' script. +If multilibs are not enabled, it does nothing, otherwise it modifies the +'Makefile' to support multilibs. - The `config-ml.in' script makes one copy of the `Makefile' for each + The 'config-ml.in' script makes one copy of the 'Makefile' for each multilib in the appropriate subdirectory. When configuring in the source directory (which is not recommended), it will build a symlink tree of the sources in each subdirectory. - The `config-ml.in' script sets several variables in the various -`Makefile's. The `Makefile.in' must have definitions for these -variables already; `config-ml.in' simply changes the existing values. -The `Makefile' should use default values for these variables which will + The 'config-ml.in' script sets several variables in the various +'Makefile's. The 'Makefile.in' must have definitions for these +variables already; 'config-ml.in' simply changes the existing values. +The 'Makefile' should use default values for these variables which will do the right thing in the subdirectories. -`MULTISRCTOP' - `config-ml.in' will set this to a sequence of `../' strings, where +'MULTISRCTOP' + 'config-ml.in' will set this to a sequence of '../' strings, where the number of strings is the number of multilib levels in the source tree. The default value should be the empty string. - -`MULTIBUILDTOP' - `config-ml.in' will set this to a sequence of `../' strings, where +'MULTIBUILDTOP' + 'config-ml.in' will set this to a sequence of '../' strings, where the number of strings is number of multilib levels in the object directory. The default value should be the empty string. This - will differ from `MULTISRCTOP' when configuring in the source tree + will differ from 'MULTISRCTOP' when configuring in the source tree (which is not recommended). - -`MULTIDIRS' - In the top level `Makefile' only, `config-ml.in' will set this to +'MULTIDIRS' + In the top level 'Makefile' only, 'config-ml.in' will set this to the list of multilib subdirectories. The default value should be the empty string. - -`MULTISUBDIR' - `config-ml.in' will set this to the installed subdirectory name to - use for this subdirectory, with a leading `/'. The default value +'MULTISUBDIR' + 'config-ml.in' will set this to the installed subdirectory name to + use for this subdirectory, with a leading '/'. The default value shold be the empty string. - -`MULTIDO' -`MULTICLEAN' - In the top level `Makefile' only, `config-ml.in' will set these +'MULTIDO' +'MULTICLEAN' + In the top level 'Makefile' only, 'config-ml.in' will set these variables to commands to use when doing a recursive make. These - variables should both default to the string `true', so that by + variables should both default to the string 'true', so that by default nothing happens. All references to the parent of the source directory should use the -variable `MULTISRCTOP'. Instead of writing `$(srcdir)/..', you must -write `$(srcdir)/$(MULTISRCTOP)..'. +variable 'MULTISRCTOP'. Instead of writing '$(srcdir)/..', you must +write '$(srcdir)/$(MULTISRCTOP)..'. Similarly, references to the parent of the object directory should -use the variable `MULTIBUILDTOP'. +use the variable 'MULTIBUILDTOP'. In the installation target, the libraries should be installed in the -subdirectory `MULTISUBDIR'. Instead of installing -`$(libdir)/libfoo.a', install `$(libdir)$(MULTISUBDIR)/libfoo.a'. +subdirectory 'MULTISUBDIR'. Instead of installing '$(libdir)/libfoo.a', +install '$(libdir)$(MULTISUBDIR)/libfoo.a'. - The `config-ml.in' script also modifies the top level `Makefile' to -add `multi-do' and `multi-clean' targets which are used when building + The 'config-ml.in' script also modifies the top level 'Makefile' to +add 'multi-do' and 'multi-clean' targets which are used when building multilibs. - The default target of the `Makefile' should include the following + The default target of the 'Makefile' should include the following command: @$(MULTIDO) $(FLAGS_TO_PASS) DO=all multi-do - This assumes that `$(FLAGS_TO_PASS)' is defined as a set of -variables to pass to a recursive invocation of `make'. This will build -all the multilibs. Note that the default value of `MULTIDO' is `true', -so by default this command will do nothing. It will only do something -in the top level `Makefile' if multilibs were enabled. +This assumes that '$(FLAGS_TO_PASS)' is defined as a set of variables to +pass to a recursive invocation of 'make'. This will build all the +multilibs. Note that the default value of 'MULTIDO' is 'true', so by +default this command will do nothing. It will only do something in the +top level 'Makefile' if multilibs were enabled. - The `install' target of the `Makefile' should include the following + The 'install' target of the 'Makefile' should include the following command: @$(MULTIDO) $(FLAGS_TO_PASS) DO=install multi-do In general, any operation, other than clean, which should be -performed on all the multilibs should use a `$(MULTIDO)' line, setting -the variable `DO' to the target of each recursive call to `make'. +performed on all the multilibs should use a '$(MULTIDO)' line, setting +the variable 'DO' to the target of each recursive call to 'make'. - The `clean' targets (`clean', `mostlyclean', etc.) should use -`$(MULTICLEAN)'. For example, the `clean' target should do this: + The 'clean' targets ('clean', 'mostlyclean', etc.) should use +'$(MULTICLEAN)'. For example, the 'clean' target should do this: @$(MULTICLEAN) DO=clean multi-clean @@ -2517,51 +2465,51 @@ File: configure.info, Node: FAQ, Next: Index, Prev: Multilibs, Up: Top 9 Frequently Asked Questions **************************** -Which do I run first, `autoconf' or `automake'? +Which do I run first, 'autoconf' or 'automake'? Except when you first add autoconf or automake support to a - package, you shouldn't run either by hand. Instead, configure - with the `--enable-maintainer-mode' option, and let `make' take - care of it. - -`autoconf' says something about undefined macros. - This means that you have macros in your `configure.in' which are - not defined by `autoconf'. You may be using an old version of - `autoconf'; try building and installing a newer one. Make sure the - newly installled `autoconf' is first on your `PATH'. Also, see - the next question. - -My `configure' script has stuff like `CY_GNU_GETTEXT' in it. - This means that you have macros in your `configure.in' which should - be defined in your `aclocal.m4' file, but aren't. This usually - means that `aclocal' was not able to appropriate definitions of the + package, you shouldn't run either by hand. Instead, configure with + the '--enable-maintainer-mode' option, and let 'make' take care of + it. + +'autoconf' says something about undefined macros. + This means that you have macros in your 'configure.in' which are + not defined by 'autoconf'. You may be using an old version of + 'autoconf'; try building and installing a newer one. Make sure the + newly installled 'autoconf' is first on your 'PATH'. Also, see the + next question. + +My 'configure' script has stuff like 'CY_GNU_GETTEXT' in it. + This means that you have macros in your 'configure.in' which should + be defined in your 'aclocal.m4' file, but aren't. This usually + means that 'aclocal' was not able to appropriate definitions of the macros. Make sure that you have installed all the packages you need. In particular, make sure that you have installed libtool - (this is where `AM_PROG_LIBTOOL' is defined) and gettext (this is - where `CY_GNU_GETTEXT' is defined, at least in the Cygnus version + (this is where 'AM_PROG_LIBTOOL' is defined) and gettext (this is + where 'CY_GNU_GETTEXT' is defined, at least in the Cygnus version of gettext). -My `Makefile' has `@' characters in it. +My 'Makefile' has '@' characters in it. This may mean that you tried to use an autoconf substitution in - your `Makefile.in' without adding the appropriate `AC_SUBST' call - to your `configure' script. Or it may just mean that you need to - rebuild `Makefile' in your build directory. To rebuild `Makefile' - from `Makefile.in', run the shell script `config.status' with no - arguments. If you need to force `configure' to run again, first - run `config.status --recheck'. These runs are normally done - automatically by `Makefile' targets, but if your `Makefile' has + your 'Makefile.in' without adding the appropriate 'AC_SUBST' call + to your 'configure' script. Or it may just mean that you need to + rebuild 'Makefile' in your build directory. To rebuild 'Makefile' + from 'Makefile.in', run the shell script 'config.status' with no + arguments. If you need to force 'configure' to run again, first + run 'config.status --recheck'. These runs are normally done + automatically by 'Makefile' targets, but if your 'Makefile' has gotten messed up you'll need to help them along. -Why do I have to run both `config.status --recheck' and `config.status'? - Normally, you don't; they will be run automatically by `Makefile' - targets. If you do need to run them, use `config.status --recheck' - to run the `configure' script again with the same arguments as the - first time you ran it. Use `config.status' (with no arguments) to - regenerate all files (`Makefile', `config.h', etc.) based on the +Why do I have to run both 'config.status --recheck' and 'config.status'? + Normally, you don't; they will be run automatically by 'Makefile' + targets. If you do need to run them, use 'config.status --recheck' + to run the 'configure' script again with the same arguments as the + first time you ran it. Use 'config.status' (with no arguments) to + regenerate all files ('Makefile', 'config.h', etc.) based on the results of the configure script. The two cases are separate - because it isn't always necessary to regenerate all the files - after running `config.status --recheck'. The `Makefile' targets + because it isn't always necessary to regenerate all the files after + running 'config.status --recheck'. The 'Makefile' targets generated by automake will use the environment variables - `CONFIG_FILES' and `CONFIG_HEADERS' to only regenerate files as + 'CONFIG_FILES' and 'CONFIG_HEADERS' to only regenerate files as they are needed. What is the Cygnus tree? @@ -2569,9 +2517,9 @@ What is the Cygnus tree? binutils, and egcs. It is also, of course, used for Cygnus releases. It is the build system which was developed at Cygnus, using the Cygnus configure script. It permits building many - different packages with a single configure and make. The - configure scripts in the tree are being converted to autoconf, but - the general build structure remains intact. + different packages with a single configure and make. The configure + scripts in the tree are being converted to autoconf, but the + general build structure remains intact. Why do I have to keep rebuilding and reinstalling the tools? I know, it's a pain. Unfortunately, there are bugs in the tools @@ -2580,12 +2528,12 @@ Why do I have to keep rebuilding and reinstalling the tools? them. I don't know if there is going to be a clever fix until the tools stabilize. -Why not just have a Cygnus tree `make' target to update the tools? +Why not just have a Cygnus tree 'make' target to update the tools? The tools unfortunately need to be installed before they can be used. That means that they must be built using an appropriate - prefix, and it seems unwise to assume that every configuration - uses an appropriate prefix. It might be possible to make them - work in place, or it might be possible to install them in some + prefix, and it seems unwise to assume that every configuration uses + an appropriate prefix. It might be possible to make them work in + place, or it might be possible to install them in some subdirectory; so far these approaches have not been implemented. @@ -2597,37 +2545,37 @@ Index * Menu: -* --build option: Build and Host Options. +* '--build' option: Build and Host Options. (line 9) -* --host option: Build and Host Options. +* '--host' option: Build and Host Options. (line 14) -* --target option: Specifying the Target. +* '--target' option: Specifying the Target. (line 10) -* _GNU_SOURCE: Write configure.in. (line 134) -* AC_CANONICAL_HOST: Using the Host Type. (line 10) -* AC_CANONICAL_SYSTEM: Using the Target Type. - (line 6) -* AC_CONFIG_HEADER: Write configure.in. (line 66) -* AC_EXEEXT: Write configure.in. (line 86) -* AC_INIT: Write configure.in. (line 38) -* AC_OUTPUT: Write configure.in. (line 142) -* AC_PREREQ: Write configure.in. (line 42) -* AC_PROG_CC: Write configure.in. (line 103) -* AC_PROG_CXX: Write configure.in. (line 117) -* acconfig.h: Written Developer Files. +* '_GNU_SOURCE': Write configure.in. (line 132) +* 'acconfig.h': Written Developer Files. (line 27) -* acconfig.h, writing: Write acconfig.h. (line 6) -* acinclude.m4: Written Developer Files. +* 'acconfig.h', writing: Write acconfig.h. (line 6) +* 'acinclude.m4': Written Developer Files. (line 37) -* aclocal.m4: Generated Developer Files. +* 'aclocal.m4': Generated Developer Files. (line 33) -* AM_CONFIG_HEADER: Write configure.in. (line 53) -* AM_DISABLE_SHARED: Write configure.in. (line 127) -* AM_EXEEXT: Write configure.in. (line 86) -* AM_INIT_AUTOMAKE: Write configure.in. (line 48) -* AM_MAINTAINER_MODE: Write configure.in. (line 70) -* AM_PROG_LIBTOOL: Write configure.in. (line 122) -* AM_PROG_LIBTOOL in configure: FAQ. (line 19) +* 'AC_CANONICAL_HOST': Using the Host Type. (line 10) +* 'AC_CANONICAL_SYSTEM': Using the Target Type. + (line 6) +* 'AC_CONFIG_HEADER': Write configure.in. (line 64) +* 'AC_EXEEXT': Write configure.in. (line 84) +* 'AC_INIT': Write configure.in. (line 37) +* 'AC_OUTPUT': Write configure.in. (line 140) +* 'AC_PREREQ': Write configure.in. (line 41) +* 'AC_PROG_CC': Write configure.in. (line 101) +* 'AC_PROG_CXX': Write configure.in. (line 115) +* 'AM_CONFIG_HEADER': Write configure.in. (line 52) +* 'AM_DISABLE_SHARED': Write configure.in. (line 125) +* 'AM_EXEEXT': Write configure.in. (line 84) +* 'AM_INIT_AUTOMAKE': Write configure.in. (line 47) +* 'AM_MAINTAINER_MODE': Write configure.in. (line 68) +* 'AM_PROG_LIBTOOL': Write configure.in. (line 120) +* 'AM_PROG_LIBTOOL' in 'configure': FAQ. (line 19) * build option: Build and Host Options. (line 9) * building with a cross compiler: Canadian Cross. (line 6) @@ -2639,20 +2587,20 @@ Index * canadian cross, configuring: Build and Host Options. (line 6) * canonical system names: Configuration Names. (line 6) -* config.cache: Build Files Description. +* 'config.cache': Build Files Description. (line 28) -* config.h: Build Files Description. +* 'config.h': Build Files Description. (line 23) -* config.h.in: Generated Developer Files. +* 'config.h.in': Generated Developer Files. (line 45) -* config.in: Generated Developer Files. +* 'config.in': Generated Developer Files. (line 45) -* config.status: Build Files Description. +* 'config.status': Build Files Description. (line 9) -* config.status --recheck: FAQ. (line 40) +* 'config.status --recheck': FAQ. (line 40) * configuration names: Configuration Names. (line 6) * configuration triplets: Configuration Names. (line 6) -* configure: Generated Developer Files. +* 'configure': Generated Developer Files. (line 21) * configure build system: Build and Host Options. (line 9) @@ -2660,9 +2608,9 @@ Index (line 14) * configure target: Specifying the Target. (line 10) -* configure.in: Written Developer Files. +* 'configure.in': Written Developer Files. (line 9) -* configure.in, writing: Write configure.in. (line 6) +* 'configure.in', writing: Write configure.in. (line 6) * configuring a canadian cross: Build and Host Options. (line 6) * cross compiler: Cross Compilation Concepts. @@ -2670,8 +2618,8 @@ Index * cross compiler, building with: Canadian Cross. (line 6) * cross tools: Cross Compilation Tools. (line 6) -* CY_GNU_GETTEXT in configure: FAQ. (line 19) * cygnus configure: Cygnus Configure. (line 6) +* 'CY_GNU_GETTEXT' in 'configure': FAQ. (line 19) * goals: Goals. (line 6) * history: History. (line 6) * host names: Configuration Names. (line 6) @@ -2679,25 +2627,25 @@ Index (line 14) * host system: Host and Target. (line 6) * host triplets: Configuration Names. (line 6) -* HOST_CC: CCross in Make. (line 27) -* libg++ configure: Cygnus Configure in C++ Libraries. +* 'HOST_CC': CCross in Make. (line 27) +* 'libg++' configure: Cygnus Configure in C++ Libraries. (line 6) -* libio configure: Cygnus Configure in C++ Libraries. +* 'libio' configure: Cygnus Configure in C++ Libraries. (line 6) -* libstdc++ configure: Cygnus Configure in C++ Libraries. +* 'libstdc++' configure: Cygnus Configure in C++ Libraries. (line 6) -* Makefile: Build Files Description. +* 'Makefile': Build Files Description. (line 18) -* Makefile, garbage characters: FAQ. (line 29) -* Makefile.am: Written Developer Files. +* 'Makefile', garbage characters: FAQ. (line 29) +* 'Makefile.am': Written Developer Files. (line 18) -* Makefile.am, writing: Write Makefile.am. (line 6) -* Makefile.in: Generated Developer Files. +* 'Makefile.am', writing: Write Makefile.am. (line 6) +* 'Makefile.in': Generated Developer Files. (line 26) * multilibs: Multilibs. (line 6) -* stamp-h: Build Files Description. - (line 41) -* stamp-h.in: Generated Developer Files. +* 'stamp-h': Build Files Description. + (line 40) +* 'stamp-h.in': Generated Developer Files. (line 54) * system names: Configuration Names. (line 6) * system types: Configuration Names. (line 6) @@ -2710,64 +2658,64 @@ Index Tag Table: -Node: Top1087 -Node: Introduction1615 -Node: Goals2697 -Node: Tools3421 -Node: History4415 -Node: Building7413 -Node: Getting Started10676 -Node: Write configure.in11189 -Node: Write Makefile.am18440 -Node: Write acconfig.h21617 -Node: Generate files23154 -Node: Getting Started Example25120 -Node: Getting Started Example 125875 -Node: Getting Started Example 227796 -Node: Getting Started Example 330791 -Node: Generate Files in Example33155 -Node: Files34245 -Node: Developer Files34856 -Node: Developer Files Picture35236 -Node: Written Developer Files36524 -Node: Generated Developer Files39076 -Node: Build Files42220 -Node: Build Files Picture42881 -Node: Build Files Description43645 -Node: Support Files45651 -Node: Configuration Names48533 -Node: Configuration Name Definition49033 -Node: Using Configuration Names51356 -Node: Cross Compilation Tools53326 -Node: Cross Compilation Concepts54017 -Node: Host and Target54985 -Node: Using the Host Type56486 -Node: Specifying the Target57835 -Node: Using the Target Type58624 -Node: Cross Tools in the Cygnus Tree62055 -Node: Host and Target Libraries63112 -Node: Target Library Configure Scripts66861 -Node: Make Targets in Cygnus Tree69953 -Node: Target libiberty71301 -Node: Canadian Cross72688 -Node: Canadian Cross Example73529 -Node: Canadian Cross Concepts74648 -Node: Build Cross Host Tools76160 -Node: Build and Host Options77112 -Node: CCross not in Cygnus Tree78898 -Node: CCross in Cygnus Tree79876 -Node: Standard Cygnus CCross80297 -Node: Cross Cygnus CCross81661 -Node: Supporting Canadian Cross84461 -Node: CCross in Configure85076 -Node: CCross in Make88244 -Node: Cygnus Configure89847 -Node: Cygnus Configure Basics90682 -Node: Cygnus Configure in C++ Libraries95360 -Node: Multilibs96367 -Node: Multilibs in gcc97412 -Node: Multilibs in Target Libraries98490 -Node: FAQ102681 -Node: Index106781 +Node: Top966 +Node: Introduction1494 +Node: Goals2576 +Node: Tools3300 +Node: History4289 +Node: Building7285 +Node: Getting Started10548 +Node: Write configure.in11061 +Node: Write Makefile.am18275 +Node: Write acconfig.h21431 +Node: Generate files22968 +Node: Getting Started Example24934 +Node: Getting Started Example 125689 +Node: Getting Started Example 227610 +Node: Getting Started Example 330605 +Node: Generate Files in Example32966 +Node: Files34052 +Node: Developer Files34663 +Node: Developer Files Picture35043 +Node: Written Developer Files36343 +Node: Generated Developer Files38895 +Node: Build Files42039 +Node: Build Files Picture42700 +Node: Build Files Description43463 +Node: Support Files45463 +Node: Configuration Names48332 +Node: Configuration Name Definition48831 +Node: Using Configuration Names51151 +Node: Cross Compilation Tools53121 +Node: Cross Compilation Concepts53812 +Node: Host and Target54780 +Node: Using the Host Type56281 +Node: Specifying the Target57628 +Node: Using the Target Type58417 +Node: Cross Tools in the Cygnus Tree61847 +Node: Host and Target Libraries62904 +Node: Target Library Configure Scripts66649 +Node: Make Targets in Cygnus Tree69741 +Node: Target libiberty71089 +Node: Canadian Cross72475 +Node: Canadian Cross Example73316 +Node: Canadian Cross Concepts74435 +Node: Build Cross Host Tools75947 +Node: Build and Host Options76899 +Node: CCross not in Cygnus Tree78685 +Node: CCross in Cygnus Tree79663 +Node: Standard Cygnus CCross80084 +Node: Cross Cygnus CCross81448 +Node: Supporting Canadian Cross84248 +Node: CCross in Configure84863 +Node: CCross in Make88028 +Node: Cygnus Configure89631 +Node: Cygnus Configure Basics90466 +Node: Cygnus Configure in C++ Libraries95144 +Node: Multilibs96151 +Node: Multilibs in gcc97196 +Node: Multilibs in Target Libraries98274 +Node: FAQ102458 +Node: Index106559 End Tag Table diff --git a/share/info/dir b/share/info/dir index 7190ca6..3af3f8b 100644 --- a/share/info/dir +++ b/share/info/dir @@ -14,6 +14,9 @@ File: dir, Node: Top This is the top of the INFO tree * Menu: +GNU Libraries +* libgomp: (libgomp). GNU OpenMP runtime library + Individual utilities * addr2line: (binutils)addr2line. Convert addresses to file and line. @@ -47,16 +50,20 @@ Individual utilities * windres: (binutils)windres. Manipulate Windows resources. Software development +* Annotate: (annotate). The obsolete annotation interface. * As: (as). The GNU assembler. * Bfd: (bfd). The Binary File Descriptor library. * Binutils: (binutils). The GNU binary utilities. * Cpp: (cpp). The GNU C preprocessor. * Cpplib: (cppinternals). Cpplib internals. * Gas: (as). The GNU assembler. +* Gdb: (gdb). The GNU debugger. * Ld: (ld). The GNU linker. +* Stabs: (stabs). The "stabs" debugging information format. * g++: (gcc). The GNU C++ compiler. * gcc: (gcc). The GNU Compiler Collection. * gccinstall: (gccinstall). Installing the GNU Compiler Collection. * gccint: (gccint). Internals of the GNU Compiler Collection. * gcov: (gcc) Gcov. `gcov'--a test coverage program. +* gdbserver: (gdb) Server. The GNU debugging server. * gprof: (gprof). Profiling your program's execution diff --git a/share/info/standards.info b/share/info/standards.info index 42942b5..4b436f0 100644 --- a/share/info/standards.info +++ b/share/info/standards.info @@ -1,12 +1,7 @@ -This is standards.info, produced by makeinfo version 4.13 from -/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.08/build/objdir/../build/../binutils/binutils-current/etc/standards.texi. +This is standards.info, produced by makeinfo version 5.1 from +standards.texi. -INFO-DIR-SECTION GNU organization -START-INFO-DIR-ENTRY -* Standards: (standards). GNU coding standards. -END-INFO-DIR-ENTRY - - The GNU coding standards, last updated April 12, 2010. +The GNU coding standards, last updated April 12, 2010. Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software @@ -18,6 +13,10 @@ any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". +INFO-DIR-SECTION GNU organization +START-INFO-DIR-ENTRY +* Standards: (standards). GNU coding standards. +END-INFO-DIR-ENTRY File: standards.info, Node: Top, Next: Preface, Prev: (dir), Up: (dir) @@ -52,7 +51,7 @@ Free Documentation License". * Index:: -File: standards.info, Node: Preface, Next: Legal Issues, Prev: Top, Up: Top +File: standards.info, Node: Preface, Next: Legal Issues, Up: Top 1 About the GNU Coding Standards ******************************** @@ -69,16 +68,16 @@ state reasons for writing in a certain way. recently, please check for a newer version. You can get the GNU Coding Standards from the GNU web server in many different formats, including the Texinfo source, PDF, HTML, DVI, plain text, and more, at: -`http://www.gnu.org/prep/standards/'. +<http://www.gnu.org/prep/standards/>. If you are maintaining an official GNU package, in addition to this document, please read and follow the GNU maintainer information (*note Contents: (maintain)Top.). If you want to receive diffs for every change to these GNU documents, -join the mailing list `gnustandards-commit@gnu.org', via the web +join the mailing list 'gnustandards-commit@gnu.org', via the web interface at -`http://lists.gnu.org/mailman/listinfo/gnustandards-commit'. Archives +<http://lists.gnu.org/mailman/listinfo/gnustandards-commit>. Archives are also available there. Please send corrections or suggestions for this document to @@ -88,7 +87,7 @@ efficiently. We prefer a context diff to the Texinfo source, but if that's difficult for you, you can make a context diff for some other version of this document, or propose it in any way that makes it clear. The source repository for this document can be found at -`http://savannah.gnu.org/projects/gnustandards'. +<http://savannah.gnu.org/projects/gnustandards>. These standards cover the minimum of what is important when writing a GNU package. Likely, the need for additional standards will come up. @@ -98,13 +97,13 @@ do suggest them. You should also set standards for your package on many questions not addressed or not firmly specified here. The most important point is to -be self-consistent--try to stick to the conventions you pick, and try -to document them as much as possible. That way, your program will be -more maintainable by others. +be self-consistent--try to stick to the conventions you pick, and try to +document them as much as possible. That way, your program will be more +maintainable by others. The GNU Hello program serves as an example of how to follow the GNU coding standards for a trivial program. -`http://www.gnu.org/software/hello/hello.html'. +<http://www.gnu.org/software/hello/hello.html>. This release of the GNU Coding Standards was last updated April 12, 2010. @@ -131,13 +130,13 @@ File: standards.info, Node: Reading Non-Free Code, Next: Contributions, Up: L ===================================== Don't in any circumstances refer to Unix source code for or during your -work on GNU! (Or to any other proprietary programs.) +work on GNU! (Or to any other proprietary programs.) If you have a vague recollection of the internals of a Unix program, -this does not absolutely mean you can't write an imitation of it, but -do try to organize the imitation internally along different lines, -because this is likely to make the details of the Unix version -irrelevant and dissimilar to your results. +this does not absolutely mean you can't write an imitation of it, but do +try to organize the imitation internally along different lines, because +this is likely to make the details of the Unix version irrelevant and +dissimilar to your results. For example, Unix utilities were generally optimized to minimize memory use; if you go for speed instead, your program will be very @@ -206,8 +205,8 @@ result. We have more detailed advice for maintainers of programs; if you have reached the stage of actually maintaining a program for GNU (whether -released or not), please ask us for a copy. It is also available -online for your perusal: `http://www.gnu.org/prep/maintain/'. +released or not), please ask us for a copy. It is also available online +for your perusal: <http://www.gnu.org/prep/maintain/>. File: standards.info, Node: Trademarks, Prev: Contributions, Up: Legal Issues @@ -226,21 +225,21 @@ there is no legal requirement for them, so we don't use them. What is legally required, as regards other people's trademarks, is to avoid using them in ways which a reader might reasonably understand as naming or labeling our own programs or activities. For example, since -"Objective C" is (or at least was) a trademark, we made sure to say -that we provide a "compiler for the Objective C language" rather than -an "Objective C compiler". The latter would have been meant as a -shorter way of saying the former, but it does not explicitly state the +"Objective C" is (or at least was) a trademark, we made sure to say that +we provide a "compiler for the Objective C language" rather than an +"Objective C compiler". The latter would have been meant as a shorter +way of saying the former, but it does not explicitly state the relationship, so it could be misinterpreted as using "Objective C" as a label for the compiler rather than for the language. Please don't use "win" as an abbreviation for Microsoft Windows in -GNU software or documentation. In hacker terminology, calling -something a "win" is a form of praise. If you wish to praise Microsoft -Windows when speaking on your own, by all means do so, but not in GNU -software. Usually we write the name "Windows" in full, but when -brevity is very important (as in file names and sometimes symbol -names), we abbreviate it to "w". For instance, the files and functions -in Emacs that deal with Windows start with `w32'. +GNU software or documentation. In hacker terminology, calling something +a "win" is a form of praise. If you wish to praise Microsoft Windows +when speaking on your own, by all means do so, but not in GNU software. +Usually we write the name "Windows" in full, but when brevity is very +important (as in file names and sometimes symbol names), we abbreviate +it to "w". For instance, the files and functions in Emacs that deal +with Windows start with 'w32'. File: standards.info, Node: Design Advice, Next: Program Behavior, Prev: Legal Issues, Up: Top @@ -266,7 +265,7 @@ File: standards.info, Node: Source Language, Next: Compatibility, Up: Design ========================== When you want to use a language that gets compiled and runs at high -speed, the best language to use is C. Using another language is like +speed, the best language to use is C. Using another language is like using a non-standard feature: it will cause trouble for users. Even if GCC supports the other language, users may find it inconvenient to have to install the compiler for that other language in order to build your @@ -288,17 +287,16 @@ alternatives. installed the other language anyway. * If an application is of interest only to a narrow part of the - community, then the question of which language it is written in - has less effect on other people, so you may as well please - yourself. + community, then the question of which language it is written in has + less effect on other people, so you may as well please yourself. Many programs are designed to be extensible: they include an -interpreter for a language that is higher level than C. Often much of +interpreter for a language that is higher level than C. Often much of the program is written in that language, too. The Emacs editor pioneered this technique. The standard extensibility interpreter for GNU software is Guile -(`http://www.gnu.org/software/guile/'), which implements the language +(<http://www.gnu.org/software/guile/>), which implements the language Scheme (an especially clean and simple dialect of Lisp). Guile also includes bindings for GTK+/GNOME, making it practical to write modern GUI functionality within Guile. We don't reject programs written in @@ -319,26 +317,26 @@ upward compatible with POSIX if POSIX specifies their behavior. When these standards conflict, it is useful to offer compatibility modes for each of them. - Standard C and POSIX prohibit many kinds of extensions. Feel free -to make the extensions anyway, and include a `--ansi', `--posix', or -`--compatible' option to turn them off. However, if the extension has -a significant chance of breaking any real programs or scripts, then it -is not really upward compatible. So you should try to redesign its + Standard C and POSIX prohibit many kinds of extensions. Feel free to +make the extensions anyway, and include a '--ansi', '--posix', or +'--compatible' option to turn them off. However, if the extension has a +significant chance of breaking any real programs or scripts, then it is +not really upward compatible. So you should try to redesign its interface to make it upward compatible. Many GNU programs suppress extensions that conflict with POSIX if the -environment variable `POSIXLY_CORRECT' is defined (even if it is -defined with a null value). Please make your program recognize this -variable if appropriate. +environment variable 'POSIXLY_CORRECT' is defined (even if it is defined +with a null value). Please make your program recognize this variable if +appropriate. When a feature is used only by users (not by programs or command files), and it is done poorly in Unix, feel free to replace it completely with something totally different and better. (For example, -`vi' is replaced with Emacs.) But it is nice to offer a compatible -feature as well. (There is a free `vi' clone, so we offer it.) +'vi' is replaced with Emacs.) But it is nice to offer a compatible +feature as well. (There is a free 'vi' clone, so we offer it.) - Additional useful features are welcome regardless of whether there -is any precedent for them. + Additional useful features are welcome regardless of whether there is +any precedent for them. File: standards.info, Node: Using Extensions, Next: Standard C, Prev: Compatibility, Up: Design Advice @@ -350,31 +348,29 @@ Many GNU facilities that already exist support a number of convenient extensions over the comparable Unix facilities. Whether to use these extensions in implementing your program is a difficult question. - On the one hand, using the extensions can make a cleaner program. -On the other hand, people will not be able to build the program unless -the other GNU tools are available. This might cause the program to -work on fewer kinds of machines. + On the one hand, using the extensions can make a cleaner program. On +the other hand, people will not be able to build the program unless the +other GNU tools are available. This might cause the program to work on +fewer kinds of machines. With some extensions, it might be easy to provide both alternatives. -For example, you can define functions with a "keyword" `INLINE' and -define that as a macro to expand into either `inline' or nothing, +For example, you can define functions with a "keyword" 'INLINE' and +define that as a macro to expand into either 'inline' or nothing, depending on the compiler. In general, perhaps it is best not to use the extensions if you can -straightforwardly do without them, but to use the extensions if they -are a big improvement. +straightforwardly do without them, but to use the extensions if they are +a big improvement. An exception to this rule are the large, established programs (such -as Emacs) which run on a great variety of systems. Using GNU -extensions in such programs would make many users unhappy, so we don't -do that. +as Emacs) which run on a great variety of systems. Using GNU extensions +in such programs would make many users unhappy, so we don't do that. Another exception is for programs that are used as part of compilation: anything that must be compiled with other compilers in -order to bootstrap the GNU compilation facilities. If these require -the GNU compiler, then no one can compile them without having them -installed already. That would be extremely troublesome in certain -cases. +order to bootstrap the GNU compilation facilities. If these require the +GNU compiler, then no one can compile them without having them installed +already. That would be extremely troublesome in certain cases. File: standards.info, Node: Standard C, Next: Conditional Compilation, Prev: Using Extensions, Up: Design Advice @@ -416,18 +412,18 @@ benefit of prototypes in all the files where the function is called. And once you have the declaration, you normally lose nothing by writing the function definition in the pre-standard style. - This technique does not work for integer types narrower than `int'. -If you think of an argument as being of a type narrower than `int', -declare it as `int' instead. + This technique does not work for integer types narrower than 'int'. +If you think of an argument as being of a type narrower than 'int', +declare it as 'int' instead. There are a few special cases where this technique is hard to use. For example, if a function argument needs to hold the system type -`dev_t', you run into trouble, because `dev_t' is shorter than `int' on -some machines; but you cannot use `int' instead, because `dev_t' is -wider than `int' on some machines. There is no type you can safely use +'dev_t', you run into trouble, because 'dev_t' is shorter than 'int' on +some machines; but you cannot use 'int' instead, because 'dev_t' is +wider than 'int' on some machines. There is no type you can safely use on all machines in a non-standard definition. The only way to support non-standard C and pass such an argument is to check the width of -`dev_t' using Autoconf and choose the argument type accordingly. This +'dev_t' using Autoconf and choose the argument type accordingly. This may not be worth the trouble. In order to support pre-standard compilers that do not recognize @@ -447,7 +443,7 @@ File: standards.info, Node: Conditional Compilation, Prev: Standard C, Up: De =========================== When supporting configuration options already known when building your -program we prefer using `if (... )' over conditional compilation, as in +program we prefer using 'if (... )' over conditional compilation, as in the former case the compiler is able to perform more extensive checking of all possible code paths. @@ -469,15 +465,15 @@ instead of: A modern compiler such as GCC will generate exactly the same code in both cases, and we have been using similar techniques with good success in several projects. Of course, the former method assumes that -`HAS_FOO' is defined as either 0 or 1. +'HAS_FOO' is defined as either 0 or 1. While this is not a silver bullet solving all portability problems, and is not always appropriate, following this policy would have saved GCC developers many hours, or even days, per year. - In the case of function-like macros like `REVERSIBLE_CC_MODE' in GCC -which cannot be simply used in `if (...)' statements, there is an easy -workaround. Simply introduce another macro `HAS_REVERSIBLE_CC_MODE' as + In the case of function-like macros like 'REVERSIBLE_CC_MODE' in GCC +which cannot be simply used in 'if (...)' statements, there is an easy +workaround. Simply introduce another macro 'HAS_REVERSIBLE_CC_MODE' as in the following example: #ifdef REVERSIBLE_CC_MODE @@ -492,8 +488,8 @@ File: standards.info, Node: Program Behavior, Next: Writing C, Prev: Design A 4 Program Behavior for All Programs *********************************** -This chapter describes conventions for writing robust software. It -also describes general standards for error messages, the command line +This chapter describes conventions for writing robust software. It also +describes general standards for error messages, the command line interface, and how libraries should behave. * Menu: @@ -526,8 +522,8 @@ overall in an objective sense. When it doesn't, you shouldn't. In most cases, following published standards is convenient for users--it means that their programs or scripts will work more portably. For instance, GCC implements nearly all the features of Standard C as -specified by that standard. C program developers would be unhappy if -it did not. And GNU utilities mostly follow specifications of POSIX.2; +specified by that standard. C program developers would be unhappy if it +did not. And GNU utilities mostly follow specifications of POSIX.2; shell script writers and users would be unhappy if our programs were incompatible. @@ -539,21 +535,20 @@ to make the GNU system better for users. prohibited. How silly! GCC implements many extensions, some of which were later adopted as part of the standard. If you want these constructs to give an error message as "required" by the standard, you -must specify `--pedantic', which was implemented only so that we can -say "GCC is a 100% implementation of the standard," not because there -is any reason to actually use it. +must specify '--pedantic', which was implemented only so that we can say +"GCC is a 100% implementation of the standard," not because there is any +reason to actually use it. - POSIX.2 specifies that `df' and `du' must output sizes by default in + POSIX.2 specifies that 'df' and 'du' must output sizes by default in units of 512 bytes. What users want is units of 1k, so that is what we -do by default. If you want the ridiculous behavior "required" by -POSIX, you must set the environment variable `POSIXLY_CORRECT' (which -was originally going to be named `POSIX_ME_HARDER'). +do by default. If you want the ridiculous behavior "required" by POSIX, +you must set the environment variable 'POSIXLY_CORRECT' (which was +originally going to be named 'POSIX_ME_HARDER'). GNU utilities also depart from the letter of the POSIX.2 specification when they support long-named command-line options, and -intermixing options with ordinary arguments. This minor -incompatibility with POSIX is never a problem in practice, and it is -very useful. +intermixing options with ordinary arguments. This minor incompatibility +with POSIX is never a problem in practice, and it is very useful. In particular, don't reject a new feature, or remove an old one, merely because a standard says it is "forbidden" or "deprecated." @@ -573,38 +568,38 @@ silently truncated". This is not acceptable in a GNU utility. nonprinting characters _including those with codes above 0177_. The only sensible exceptions would be utilities specifically intended for interface to certain types of terminals or printers that can't handle -those characters. Whenever possible, try to make programs work -properly with sequences of bytes that represent multibyte characters, -using encodings such as UTF-8 and others. +those characters. Whenever possible, try to make programs work properly +with sequences of bytes that represent multibyte characters, using +encodings such as UTF-8 and others. - Check every system call for an error return, unless you know you -wish to ignore errors. Include the system error text (from `perror' or + Check every system call for an error return, unless you know you wish +to ignore errors. Include the system error text (from 'perror' or equivalent) in _every_ error message resulting from a failing system call, as well as the name of the file if any and the name of the utility. Just "cannot open foo.c" or "stat failed" is not sufficient. - Check every call to `malloc' or `realloc' to see if it returned -zero. Check `realloc' even if you are making the block smaller; in a -system that rounds block sizes to a power of 2, `realloc' may get a -different block if you ask for less space. + Check every call to 'malloc' or 'realloc' to see if it returned zero. +Check 'realloc' even if you are making the block smaller; in a system +that rounds block sizes to a power of 2, 'realloc' may get a different +block if you ask for less space. - In Unix, `realloc' can destroy the storage block if it returns zero. -GNU `realloc' does not have this bug: if it fails, the original block -is unchanged. Feel free to assume the bug is fixed. If you wish to -run your program on Unix, and wish to avoid lossage in this case, you -can use the GNU `malloc'. + In Unix, 'realloc' can destroy the storage block if it returns zero. +GNU 'realloc' does not have this bug: if it fails, the original block is +unchanged. Feel free to assume the bug is fixed. If you wish to run +your program on Unix, and wish to avoid lossage in this case, you can +use the GNU 'malloc'. - You must expect `free' to alter the contents of the block that was + You must expect 'free' to alter the contents of the block that was freed. Anything you want to fetch from the block, you must fetch before -calling `free'. +calling 'free'. - If `malloc' fails in a noninteractive program, make that a fatal + If 'malloc' fails in a noninteractive program, make that a fatal error. In an interactive program (one that reads commands from the user), it is better to abort the command and return to the command reader loop. This allows the user to kill other processes to free up virtual memory, and then try the command again. - Use `getopt_long' to decode arguments, unless the argument syntax + Use 'getopt_long' to decode arguments, unless the argument syntax makes this unreasonable. When static storage is to be written in during program execution, use @@ -614,19 +609,19 @@ for data that will not be changed. Try to avoid low-level interfaces to obscure Unix data structures (such as file directories, utmp, or the layout of kernel memory), since these are less likely to work compatibly. If you need to find all the -files in a directory, use `readdir' or some other high-level interface. +files in a directory, use 'readdir' or some other high-level interface. These are supported compatibly by GNU. The preferred signal handling facilities are the BSD variant of -`signal', and the POSIX `sigaction' function; the alternative USG -`signal' interface is an inferior design. +'signal', and the POSIX 'sigaction' function; the alternative USG +'signal' interface is an inferior design. Nowadays, using the POSIX signal functions may be the easiest way to -make a program portable. If you use `signal', then on GNU/Linux -systems running GNU libc version 1, you should include `bsd/signal.h' -instead of `signal.h', so as to get BSD behavior. It is up to you -whether to support systems where `signal' has only the USG behavior, or -give up on them. +make a program portable. If you use 'signal', then on GNU/Linux systems +running GNU libc version 1, you should include 'bsd/signal.h' instead of +'signal.h', so as to get BSD behavior. It is up to you whether to +support systems where 'signal' has only the USG behavior, or give up on +them. In error checks that detect "impossible" conditions, just abort. There is usually no point in printing any message. These checks @@ -636,15 +631,15 @@ comments in the source. The relevant data will be in variables, which are easy to examine with the debugger, so there is no point moving them elsewhere. - Do not use a count of errors as the exit status for a program. -_That does not work_, because exit status values are limited to 8 bits -(0 through 255). A single run of the program might have 256 errors; if -you try to return 256 as the exit status, the parent process will see 0 -as the status, and it will appear that the program succeeded. + Do not use a count of errors as the exit status for a program. _That +does not work_, because exit status values are limited to 8 bits (0 +through 255). A single run of the program might have 256 errors; if you +try to return 256 as the exit status, the parent process will see 0 as +the status, and it will appear that the program succeeded. - If you make temporary files, check the `TMPDIR' environment -variable; if that variable is defined, use the specified directory -instead of `/tmp'. + If you make temporary files, check the 'TMPDIR' environment variable; +if that variable is defined, use the specified directory instead of +'/tmp'. In addition, be aware that there is a possible security problem when creating temporary files in world-writable directories. In C, you can @@ -652,9 +647,9 @@ avoid this problem by creating temporary files in this manner: fd = open (filename, O_WRONLY | O_CREAT | O_EXCL, 0600); -or by using the `mkstemps' function from libiberty. +or by using the 'mkstemps' function from libiberty. - In bash, use `set -C' to avoid this problem. + In bash, use 'set -C' to avoid this problem. File: standards.info, Node: Libraries, Next: Errors, Prev: Semantics, Up: Program Behavior @@ -664,7 +659,7 @@ File: standards.info, Node: Libraries, Next: Errors, Prev: Semantics, Up: Pr Try to make library functions reentrant. If they need to do dynamic storage allocation, at least try to avoid any nonreentrancy aside from -that of `malloc' itself. +that of 'malloc' itself. Here are certain name conventions for libraries, to avoid name conflicts. @@ -675,14 +670,14 @@ In addition, there should only be one of these in any given library member. This usually means putting each one in a separate source file. An exception can be made when two external symbols are always used -together, so that no reasonable program could use one without the -other; then they can both go in the same file. +together, so that no reasonable program could use one without the other; +then they can both go in the same file. External symbols that are not documented entry points for the user -should have names beginning with `_'. The `_' should be followed by -the chosen name prefix for the library, to prevent collisions with -other libraries. These can go in the same files with user entry points -if you like. +should have names beginning with '_'. The '_' should be followed by the +chosen name prefix for the library, to prevent collisions with other +libraries. These can go in the same files with user entry points if you +like. Static functions and variables can be used as you like and need not fit any naming convention. @@ -705,8 +700,8 @@ If you want to mention the column number, use one of these formats: Line numbers should start from 1 at the beginning of the file, and column numbers should start from 1 at the beginning of the line. (Both of these conventions are chosen for compatibility.) Calculate column -numbers assuming that space and all ASCII printing characters have -equal width, and assuming tab stops every 8 columns. +numbers assuming that space and all ASCII printing characters have equal +width, and assuming tab stops every 8 columns. The error message can also give both the starting and ending positions of the erroneous text. There are several formats so that you @@ -779,11 +774,11 @@ is useful with output to a terminal, and have an option for the other behavior. Compatibility requires certain programs to depend on the type of -output device. It would be disastrous if `ls' or `sh' did not do so in +output device. It would be disastrous if 'ls' or 'sh' did not do so in the way all users expect. In some of these cases, we supplement the program with a preferred alternate version that does not depend on the -output device type. For example, we provide a `dir' program much like -`ls' except that its default output format is always multi-column +output device type. For example, we provide a 'dir' program much like +'ls' except that its default output format is always multi-column format. @@ -793,9 +788,9 @@ File: standards.info, Node: Graphical Interfaces, Next: Command-Line Interface ====================================== When you write a program that provides a graphical user interface, -please make it work with the X Window System and the GTK+ toolkit -unless the functionality specifically requires some alternative (for -example, "displaying jpeg images while in console mode"). +please make it work with the X Window System and the GTK+ toolkit unless +the functionality specifically requires some alternative (for example, +"displaying jpeg images while in console mode"). In addition, please provide a command-line interface to control the functionality. (In many cases, the graphical user interface can be a @@ -803,12 +798,12 @@ separate program which invokes the command-line program.) This is so that the same jobs can be done from scripts. Please also consider providing a D-bus interface for use from other -running programs, such as within GNOME. (GNOME used to use CORBA for +running programs, such as within GNOME. (GNOME used to use CORBA for this, but that is being phased out.) In addition, consider providing a library interface (for use from C), and perhaps a keyboard-driven console interface (for use by users from console mode). Once you are -doing the work to provide the functionality and the graphical -interface, these won't be much extra work. +doing the work to provide the functionality and the graphical interface, +these won't be much extra work. File: standards.info, Node: Command-Line Interfaces, Next: Option Table, Prev: Graphical Interfaces, Up: Program Behavior @@ -817,48 +812,48 @@ File: standards.info, Node: Command-Line Interfaces, Next: Option Table, Prev ========================================= It is a good idea to follow the POSIX guidelines for the command-line -options of a program. The easiest way to do this is to use `getopt' to -parse them. Note that the GNU version of `getopt' will normally permit -options anywhere among the arguments unless the special argument `--' -is used. This is not what POSIX specifies; it is a GNU extension. +options of a program. The easiest way to do this is to use 'getopt' to +parse them. Note that the GNU version of 'getopt' will normally permit +options anywhere among the arguments unless the special argument '--' is +used. This is not what POSIX specifies; it is a GNU extension. Please define long-named options that are equivalent to the single-letter Unix-style options. We hope to make GNU more user friendly this way. This is easy to do with the GNU function -`getopt_long'. +'getopt_long'. One of the advantages of long-named options is that they can be consistent from program to program. For example, users should be able to expect the "verbose" option of any GNU program which has one, to be -spelled precisely `--verbose'. To achieve this uniformity, look at the +spelled precisely '--verbose'. To achieve this uniformity, look at the table of common long-option names when you choose the option names for your program (*note Option Table::). It is usually a good idea for file names given as ordinary arguments to be input files only; any output files would be specified using -options (preferably `-o' or `--output'). Even if you allow an output +options (preferably '-o' or '--output'). Even if you allow an output file name as an ordinary argument for compatibility, try to provide an option as another way to specify it. This will lead to more consistency among GNU utilities, and fewer idiosyncrasies for users to remember. - All programs should support two standard options: `--version' and -`--help'. CGI programs should accept these as command-line options, -and also if given as the `PATH_INFO'; for instance, visiting -`http://example.org/p.cgi/--help' in a browser should output the same -information as invoking `p.cgi --help' from the command line. + All programs should support two standard options: '--version' and +'--help'. CGI programs should accept these as command-line options, and +also if given as the 'PATH_INFO'; for instance, visiting +<http://example.org/p.cgi/--help> in a browser should output the same +information as invoking 'p.cgi --help' from the command line. * Menu: -* --version:: The standard output for --version. -* --help:: The standard output for --help. +* --version:: The standard output for -version. +* --help:: The standard output for -help. File: standards.info, Node: --version, Next: --help, Up: Command-Line Interfaces -4.7.1 `--version' +4.7.1 '--version' ----------------- -The standard `--version' option should direct the program to print +The standard '--version' option should direct the program to print information about its name, version, origin and legal status, all on standard output, and then exit successfully. Other options and arguments should be ignored once this is seen, and the program should @@ -871,9 +866,9 @@ contains the canonical name for this program, in this format: GNU Emacs 19.30 The program's name should be a constant string; _don't_ compute it from -`argv[0]'. The idea is to state the standard or canonical name for the +'argv[0]'. The idea is to state the standard or canonical name for the program, not its file name. There are other ways to find out the -precise file name where a command is found in `PATH'. +precise file name where a command is found in 'PATH'. If the program is a subsidiary part of a larger package, mention the package name in parentheses, like this: @@ -885,8 +880,8 @@ program's version number, you can mention the package version number just before the close-parenthesis. If you _need_ to mention the version numbers of libraries which are -distributed separately from the package which contains this program, -you can do so by printing an additional line of version info for each +distributed separately from the package which contains this program, you +can do so by printing an additional line of version info for each library you want to mention. Use the same format for these lines as for the first line. @@ -895,9 +890,9 @@ the first line. Please mention library version numbers only if you find in practice that they are very important to you in debugging. - The following line, after the version number line or lines, should -be a copyright notice. If more than one copyright notice is called -for, put each on a separate line. + The following line, after the version number line or lines, should be +a copyright notice. If more than one copyright notice is called for, +put each on a separate line. Next should follow a line stating the license, preferably using one of abbrevations below, and a brief statement that the program is free @@ -925,11 +920,11 @@ which changes were made--there's no need to list the years for previous versions' changes. You don't have to mention the name of the program in these notices, if that is inconvenient, since it appeared in the first line. (The rules are different for copyright notices in source files; -*note Copyright Notices: (maintain)Copyright Notices.) +*note (maintain)Copyright Notices::.) Translations of the above lines must preserve the validity of the copyright notices (*note Internationalization::). If the translation's -character set supports it, the `(C)' should be replaced with the +character set supports it, the '(C)' should be replaced with the copyright symbol, as follows: (the official copyright symbol, which is the letter C in a circle); @@ -940,80 +935,79 @@ the English word "Copyright"; translations into other languages do not have legal significance. Finally, here is the table of our suggested license abbreviations. -Any abbreviation can be followed by `vVERSION[+]', meaning that -particular version, or later versions with the `+', as shown above. +Any abbreviation can be followed by 'vVERSION[+]', meaning that +particular version, or later versions with the '+', as shown above. In the case of exceptions for extra permissions with the GPL, we use -`/' for a separator; the version number can follow the license +'/' for a separator; the version number can follow the license abbreviation as usual, as in the examples below. GPL - GNU General Public License, `http://www.gnu.org/licenses/gpl.html'. + GNU General Public License, <http://www.gnu.org/licenses/gpl.html>. LGPL GNU Lesser General Public License, - `http://www.gnu.org/licenses/lgpl.html'. + <http://www.gnu.org/licenses/lgpl.html>. GPL/Ada GNU GPL with the exception for Ada. Apache The Apache Software Foundation license, - `http://www.apache.org/licenses'. + <http://www.apache.org/licenses>. Artistic The Artistic license used for Perl, - `http://www.perlfoundation.org/legal'. + <http://www.perlfoundation.org/legal>. Expat - The Expat license, `http://www.jclark.com/xml/copying.txt'. + The Expat license, <http://www.jclark.com/xml/copying.txt>. MPL - The Mozilla Public License, `http://www.mozilla.org/MPL/'. + The Mozilla Public License, <http://www.mozilla.org/MPL/>. OBSD The original (4-clause) BSD license, incompatible with the GNU GPL - `http://www.xfree86.org/3.3.6/COPYRIGHT2.html#6'. + <http://www.xfree86.org/3.3.6/COPYRIGHT2.html#6>. PHP - The license used for PHP, `http://www.php.net/license/'. + The license used for PHP, <http://www.php.net/license/>. public domain The non-license that is being in the public domain, - `http://www.gnu.org/licenses/license-list.html#PublicDomain'. + <http://www.gnu.org/licenses/license-list.html#PublicDomain>. Python - The license for Python, `http://www.python.org/2.0.1/license.html'. + The license for Python, <http://www.python.org/2.0.1/license.html>. RBSD The revised (3-clause) BSD, compatible with the GNU GPL, - `http://www.xfree86.org/3.3.6/COPYRIGHT2.html#5'. + <http://www.xfree86.org/3.3.6/COPYRIGHT2.html#5>. X11 The simple non-copyleft license used for most versions of the X - Window System, `http://www.xfree86.org/3.3.6/COPYRIGHT2.html#3'. + Window System, <http://www.xfree86.org/3.3.6/COPYRIGHT2.html#3>. Zlib - The license for Zlib, `http://www.gzip.org/zlib/zlib_license.html'. - + The license for Zlib, <http://www.gzip.org/zlib/zlib_license.html>. More information about these licenses and many more are on the GNU -licensing web pages, `http://www.gnu.org/licenses/license-list.html'. +licensing web pages, <http://www.gnu.org/licenses/license-list.html>. File: standards.info, Node: --help, Prev: --version, Up: Command-Line Interfaces -4.7.2 `--help' +4.7.2 '--help' -------------- -The standard `--help' option should output brief documentation for how +The standard '--help' option should output brief documentation for how to invoke the program, on standard output, then exit successfully. -Other options and arguments should be ignored once this is seen, and -the program should not perform its normal function. +Other options and arguments should be ignored once this is seen, and the +program should not perform its normal function. - Near the end of the `--help' option's output, please place lines + Near the end of the '--help' option's output, please place lines giving the email address for bug reports, the package's home page -(normally <http://www.gnu.org/software/PKG>, and the general page for +(normally 'http://www.gnu.org/software/PKG', and the general page for help using GNU programs. The format should be like this: Report bugs to: MAILING-ADDRESS @@ -1031,1087 +1025,1087 @@ File: standards.info, Node: Option Table, Next: OID Allocations, Prev: Comman Here is a table of long options used by GNU programs. It is surely incomplete, but we aim to list all the options that a new program might want to be compatible with. If you use names not already in the table, -please send <bug-standards@gnu.org> a list of them, with their -meanings, so we can update the table. +please send <bug-standards@gnu.org> a list of them, with their meanings, +so we can update the table. -`after-date' - `-N' in `tar'. +'after-date' + '-N' in 'tar'. -`all' - `-a' in `du', `ls', `nm', `stty', `uname', and `unexpand'. +'all' + '-a' in 'du', 'ls', 'nm', 'stty', 'uname', and 'unexpand'. -`all-text' - `-a' in `diff'. +'all-text' + '-a' in 'diff'. -`almost-all' - `-A' in `ls'. +'almost-all' + '-A' in 'ls'. -`append' - `-a' in `etags', `tee', `time'; `-r' in `tar'. +'append' + '-a' in 'etags', 'tee', 'time'; '-r' in 'tar'. -`archive' - `-a' in `cp'. +'archive' + '-a' in 'cp'. -`archive-name' - `-n' in `shar'. +'archive-name' + '-n' in 'shar'. -`arglength' - `-l' in `m4'. +'arglength' + '-l' in 'm4'. -`ascii' - `-a' in `diff'. +'ascii' + '-a' in 'diff'. -`assign' - `-v' in `gawk'. +'assign' + '-v' in 'gawk'. -`assume-new' - `-W' in `make'. +'assume-new' + '-W' in 'make'. -`assume-old' - `-o' in `make'. +'assume-old' + '-o' in 'make'. -`auto-check' - `-a' in `recode'. +'auto-check' + '-a' in 'recode'. -`auto-pager' - `-a' in `wdiff'. +'auto-pager' + '-a' in 'wdiff'. -`auto-reference' - `-A' in `ptx'. +'auto-reference' + '-A' in 'ptx'. -`avoid-wraps' - `-n' in `wdiff'. +'avoid-wraps' + '-n' in 'wdiff'. -`background' +'background' For server programs, run in the background. -`backward-search' - `-B' in `ctags'. +'backward-search' + '-B' in 'ctags'. -`basename' - `-f' in `shar'. +'basename' + '-f' in 'shar'. -`batch' +'batch' Used in GDB. -`baud' +'baud' Used in GDB. -`before' - `-b' in `tac'. +'before' + '-b' in 'tac'. -`binary' - `-b' in `cpio' and `diff'. +'binary' + '-b' in 'cpio' and 'diff'. -`bits-per-code' - `-b' in `shar'. +'bits-per-code' + '-b' in 'shar'. -`block-size' - Used in `cpio' and `tar'. +'block-size' + Used in 'cpio' and 'tar'. -`blocks' - `-b' in `head' and `tail'. +'blocks' + '-b' in 'head' and 'tail'. -`break-file' - `-b' in `ptx'. +'break-file' + '-b' in 'ptx'. -`brief' +'brief' Used in various programs to make output shorter. -`bytes' - `-c' in `head', `split', and `tail'. +'bytes' + '-c' in 'head', 'split', and 'tail'. -`c++' - `-C' in `etags'. +'c++' + '-C' in 'etags'. -`catenate' - `-A' in `tar'. +'catenate' + '-A' in 'tar'. -`cd' +'cd' Used in various programs to specify the directory to use. -`changes' - `-c' in `chgrp' and `chown'. +'changes' + '-c' in 'chgrp' and 'chown'. -`classify' - `-F' in `ls'. +'classify' + '-F' in 'ls'. -`colons' - `-c' in `recode'. +'colons' + '-c' in 'recode'. -`command' - `-c' in `su'; `-x' in GDB. +'command' + '-c' in 'su'; '-x' in GDB. -`compare' - `-d' in `tar'. +'compare' + '-d' in 'tar'. -`compat' - Used in `gawk'. +'compat' + Used in 'gawk'. -`compress' - `-Z' in `tar' and `shar'. +'compress' + '-Z' in 'tar' and 'shar'. -`concatenate' - `-A' in `tar'. +'concatenate' + '-A' in 'tar'. -`confirmation' - `-w' in `tar'. +'confirmation' + '-w' in 'tar'. -`context' - Used in `diff'. +'context' + Used in 'diff'. -`copyleft' - `-W copyleft' in `gawk'. +'copyleft' + '-W copyleft' in 'gawk'. -`copyright' - `-C' in `ptx', `recode', and `wdiff'; `-W copyright' in `gawk'. +'copyright' + '-C' in 'ptx', 'recode', and 'wdiff'; '-W copyright' in 'gawk'. -`core' +'core' Used in GDB. -`count' - `-q' in `who'. +'count' + '-q' in 'who'. -`count-links' - `-l' in `du'. +'count-links' + '-l' in 'du'. -`create' - Used in `tar' and `cpio'. +'create' + Used in 'tar' and 'cpio'. -`cut-mark' - `-c' in `shar'. +'cut-mark' + '-c' in 'shar'. -`cxref' - `-x' in `ctags'. +'cxref' + '-x' in 'ctags'. -`date' - `-d' in `touch'. +'date' + '-d' in 'touch'. -`debug' - `-d' in `make' and `m4'; `-t' in Bison. +'debug' + '-d' in 'make' and 'm4'; '-t' in Bison. -`define' - `-D' in `m4'. +'define' + '-D' in 'm4'. -`defines' - `-d' in Bison and `ctags'. +'defines' + '-d' in Bison and 'ctags'. -`delete' - `-D' in `tar'. +'delete' + '-D' in 'tar'. -`dereference' - `-L' in `chgrp', `chown', `cpio', `du', `ls', and `tar'. +'dereference' + '-L' in 'chgrp', 'chown', 'cpio', 'du', 'ls', and 'tar'. -`dereference-args' - `-D' in `du'. +'dereference-args' + '-D' in 'du'. -`device' +'device' Specify an I/O device (special file name). -`diacritics' - `-d' in `recode'. +'diacritics' + '-d' in 'recode'. -`dictionary-order' - `-d' in `look'. +'dictionary-order' + '-d' in 'look'. -`diff' - `-d' in `tar'. +'diff' + '-d' in 'tar'. -`digits' - `-n' in `csplit'. +'digits' + '-n' in 'csplit'. -`directory' - Specify the directory to use, in various programs. In `ls', it +'directory' + Specify the directory to use, in various programs. In 'ls', it means to show directories themselves rather than their contents. - In `rm' and `ln', it means to not treat links to directories + In 'rm' and 'ln', it means to not treat links to directories specially. -`discard-all' - `-x' in `strip'. +'discard-all' + '-x' in 'strip'. -`discard-locals' - `-X' in `strip'. +'discard-locals' + '-X' in 'strip'. -`dry-run' - `-n' in `make'. +'dry-run' + '-n' in 'make'. -`ed' - `-e' in `diff'. +'ed' + '-e' in 'diff'. -`elide-empty-files' - `-z' in `csplit'. +'elide-empty-files' + '-z' in 'csplit'. -`end-delete' - `-x' in `wdiff'. +'end-delete' + '-x' in 'wdiff'. -`end-insert' - `-z' in `wdiff'. +'end-insert' + '-z' in 'wdiff'. -`entire-new-file' - `-N' in `diff'. +'entire-new-file' + '-N' in 'diff'. -`environment-overrides' - `-e' in `make'. +'environment-overrides' + '-e' in 'make'. -`eof' - `-e' in `xargs'. +'eof' + '-e' in 'xargs'. -`epoch' +'epoch' Used in GDB. -`error-limit' - Used in `makeinfo'. +'error-limit' + Used in 'makeinfo'. -`error-output' - `-o' in `m4'. +'error-output' + '-o' in 'm4'. -`escape' - `-b' in `ls'. +'escape' + '-b' in 'ls'. -`exclude-from' - `-X' in `tar'. +'exclude-from' + '-X' in 'tar'. -`exec' +'exec' Used in GDB. -`exit' - `-x' in `xargs'. +'exit' + '-x' in 'xargs'. -`exit-0' - `-e' in `unshar'. +'exit-0' + '-e' in 'unshar'. -`expand-tabs' - `-t' in `diff'. +'expand-tabs' + '-t' in 'diff'. -`expression' - `-e' in `sed'. +'expression' + '-e' in 'sed'. -`extern-only' - `-g' in `nm'. +'extern-only' + '-g' in 'nm'. -`extract' - `-i' in `cpio'; `-x' in `tar'. +'extract' + '-i' in 'cpio'; '-x' in 'tar'. -`faces' - `-f' in `finger'. +'faces' + '-f' in 'finger'. -`fast' - `-f' in `su'. +'fast' + '-f' in 'su'. -`fatal-warnings' - `-E' in `m4'. +'fatal-warnings' + '-E' in 'm4'. -`file' - `-f' in `gawk', `info', `make', `mt', `sed', and `tar'. +'file' + '-f' in 'gawk', 'info', 'make', 'mt', 'sed', and 'tar'. -`field-separator' - `-F' in `gawk'. +'field-separator' + '-F' in 'gawk'. -`file-prefix' - `-b' in Bison. +'file-prefix' + '-b' in Bison. -`file-type' - `-F' in `ls'. +'file-type' + '-F' in 'ls'. -`files-from' - `-T' in `tar'. +'files-from' + '-T' in 'tar'. -`fill-column' - Used in `makeinfo'. +'fill-column' + Used in 'makeinfo'. -`flag-truncation' - `-F' in `ptx'. +'flag-truncation' + '-F' in 'ptx'. -`fixed-output-files' - `-y' in Bison. +'fixed-output-files' + '-y' in Bison. -`follow' - `-f' in `tail'. +'follow' + '-f' in 'tail'. -`footnote-style' - Used in `makeinfo'. +'footnote-style' + Used in 'makeinfo'. -`force' - `-f' in `cp', `ln', `mv', and `rm'. +'force' + '-f' in 'cp', 'ln', 'mv', and 'rm'. -`force-prefix' - `-F' in `shar'. +'force-prefix' + '-F' in 'shar'. -`foreground' +'foreground' For server programs, run in the foreground; in other words, don't do anything special to run the server in the background. -`format' - Used in `ls', `time', and `ptx'. +'format' + Used in 'ls', 'time', and 'ptx'. -`freeze-state' - `-F' in `m4'. +'freeze-state' + '-F' in 'm4'. -`fullname' +'fullname' Used in GDB. -`gap-size' - `-g' in `ptx'. +'gap-size' + '-g' in 'ptx'. -`get' - `-x' in `tar'. +'get' + '-x' in 'tar'. -`graphic' - `-i' in `ul'. +'graphic' + '-i' in 'ul'. -`graphics' - `-g' in `recode'. +'graphics' + '-g' in 'recode'. -`group' - `-g' in `install'. +'group' + '-g' in 'install'. -`gzip' - `-z' in `tar' and `shar'. +'gzip' + '-z' in 'tar' and 'shar'. -`hashsize' - `-H' in `m4'. +'hashsize' + '-H' in 'm4'. -`header' - `-h' in `objdump' and `recode' +'header' + '-h' in 'objdump' and 'recode' -`heading' - `-H' in `who'. +'heading' + '-H' in 'who'. -`help' +'help' Used to ask for brief usage information. -`here-delimiter' - `-d' in `shar'. +'here-delimiter' + '-d' in 'shar'. -`hide-control-chars' - `-q' in `ls'. +'hide-control-chars' + '-q' in 'ls'. -`html' - In `makeinfo', output HTML. +'html' + In 'makeinfo', output HTML. -`idle' - `-u' in `who'. +'idle' + '-u' in 'who'. -`ifdef' - `-D' in `diff'. +'ifdef' + '-D' in 'diff'. -`ignore' - `-I' in `ls'; `-x' in `recode'. +'ignore' + '-I' in 'ls'; '-x' in 'recode'. -`ignore-all-space' - `-w' in `diff'. +'ignore-all-space' + '-w' in 'diff'. -`ignore-backups' - `-B' in `ls'. +'ignore-backups' + '-B' in 'ls'. -`ignore-blank-lines' - `-B' in `diff'. +'ignore-blank-lines' + '-B' in 'diff'. -`ignore-case' - `-f' in `look' and `ptx'; `-i' in `diff' and `wdiff'. +'ignore-case' + '-f' in 'look' and 'ptx'; '-i' in 'diff' and 'wdiff'. -`ignore-errors' - `-i' in `make'. +'ignore-errors' + '-i' in 'make'. -`ignore-file' - `-i' in `ptx'. +'ignore-file' + '-i' in 'ptx'. -`ignore-indentation' - `-I' in `etags'. +'ignore-indentation' + '-I' in 'etags'. -`ignore-init-file' - `-f' in Oleo. +'ignore-init-file' + '-f' in Oleo. -`ignore-interrupts' - `-i' in `tee'. +'ignore-interrupts' + '-i' in 'tee'. -`ignore-matching-lines' - `-I' in `diff'. +'ignore-matching-lines' + '-I' in 'diff'. -`ignore-space-change' - `-b' in `diff'. +'ignore-space-change' + '-b' in 'diff'. -`ignore-zeros' - `-i' in `tar'. +'ignore-zeros' + '-i' in 'tar'. -`include' - `-i' in `etags'; `-I' in `m4'. +'include' + '-i' in 'etags'; '-I' in 'm4'. -`include-dir' - `-I' in `make'. +'include-dir' + '-I' in 'make'. -`incremental' - `-G' in `tar'. +'incremental' + '-G' in 'tar'. -`info' - `-i', `-l', and `-m' in Finger. +'info' + '-i', '-l', and '-m' in Finger. -`init-file' +'init-file' In some programs, specify the name of the file to read as the user's init file. -`initial' - `-i' in `expand'. +'initial' + '-i' in 'expand'. -`initial-tab' - `-T' in `diff'. +'initial-tab' + '-T' in 'diff'. -`inode' - `-i' in `ls'. +'inode' + '-i' in 'ls'. -`interactive' - `-i' in `cp', `ln', `mv', `rm'; `-e' in `m4'; `-p' in `xargs'; - `-w' in `tar'. +'interactive' + '-i' in 'cp', 'ln', 'mv', 'rm'; '-e' in 'm4'; '-p' in 'xargs'; '-w' + in 'tar'. -`intermix-type' - `-p' in `shar'. +'intermix-type' + '-p' in 'shar'. -`iso-8601' - Used in `date' +'iso-8601' + Used in 'date' -`jobs' - `-j' in `make'. +'jobs' + '-j' in 'make'. -`just-print' - `-n' in `make'. +'just-print' + '-n' in 'make'. -`keep-going' - `-k' in `make'. +'keep-going' + '-k' in 'make'. -`keep-files' - `-k' in `csplit'. +'keep-files' + '-k' in 'csplit'. -`kilobytes' - `-k' in `du' and `ls'. +'kilobytes' + '-k' in 'du' and 'ls'. -`language' - `-l' in `etags'. +'language' + '-l' in 'etags'. -`less-mode' - `-l' in `wdiff'. +'less-mode' + '-l' in 'wdiff'. -`level-for-gzip' - `-g' in `shar'. +'level-for-gzip' + '-g' in 'shar'. -`line-bytes' - `-C' in `split'. +'line-bytes' + '-C' in 'split'. -`lines' - Used in `split', `head', and `tail'. +'lines' + Used in 'split', 'head', and 'tail'. -`link' - `-l' in `cpio'. +'link' + '-l' in 'cpio'. -`lint' -`lint-old' - Used in `gawk'. +'lint' +'lint-old' + Used in 'gawk'. -`list' - `-t' in `cpio'; `-l' in `recode'. +'list' + '-t' in 'cpio'; '-l' in 'recode'. -`list' - `-t' in `tar'. +'list' + '-t' in 'tar'. -`literal' - `-N' in `ls'. +'literal' + '-N' in 'ls'. -`load-average' - `-l' in `make'. +'load-average' + '-l' in 'make'. -`login' - Used in `su'. +'login' + Used in 'su'. -`machine' - Used in `uname'. +'machine' + Used in 'uname'. -`macro-name' - `-M' in `ptx'. +'macro-name' + '-M' in 'ptx'. -`mail' - `-m' in `hello' and `uname'. +'mail' + '-m' in 'hello' and 'uname'. -`make-directories' - `-d' in `cpio'. +'make-directories' + '-d' in 'cpio'. -`makefile' - `-f' in `make'. +'makefile' + '-f' in 'make'. -`mapped' +'mapped' Used in GDB. -`max-args' - `-n' in `xargs'. +'max-args' + '-n' in 'xargs'. -`max-chars' - `-n' in `xargs'. +'max-chars' + '-n' in 'xargs'. -`max-lines' - `-l' in `xargs'. +'max-lines' + '-l' in 'xargs'. -`max-load' - `-l' in `make'. +'max-load' + '-l' in 'make'. -`max-procs' - `-P' in `xargs'. +'max-procs' + '-P' in 'xargs'. -`mesg' - `-T' in `who'. +'mesg' + '-T' in 'who'. -`message' - `-T' in `who'. +'message' + '-T' in 'who'. -`minimal' - `-d' in `diff'. +'minimal' + '-d' in 'diff'. -`mixed-uuencode' - `-M' in `shar'. +'mixed-uuencode' + '-M' in 'shar'. -`mode' - `-m' in `install', `mkdir', and `mkfifo'. +'mode' + '-m' in 'install', 'mkdir', and 'mkfifo'. -`modification-time' - `-m' in `tar'. +'modification-time' + '-m' in 'tar'. -`multi-volume' - `-M' in `tar'. +'multi-volume' + '-M' in 'tar'. -`name-prefix' - `-a' in Bison. +'name-prefix' + '-a' in Bison. -`nesting-limit' - `-L' in `m4'. +'nesting-limit' + '-L' in 'm4'. -`net-headers' - `-a' in `shar'. +'net-headers' + '-a' in 'shar'. -`new-file' - `-W' in `make'. +'new-file' + '-W' in 'make'. -`no-builtin-rules' - `-r' in `make'. +'no-builtin-rules' + '-r' in 'make'. -`no-character-count' - `-w' in `shar'. +'no-character-count' + '-w' in 'shar'. -`no-check-existing' - `-x' in `shar'. +'no-check-existing' + '-x' in 'shar'. -`no-common' - `-3' in `wdiff'. +'no-common' + '-3' in 'wdiff'. -`no-create' - `-c' in `touch'. +'no-create' + '-c' in 'touch'. -`no-defines' - `-D' in `etags'. +'no-defines' + '-D' in 'etags'. -`no-deleted' - `-1' in `wdiff'. +'no-deleted' + '-1' in 'wdiff'. -`no-dereference' - `-d' in `cp'. +'no-dereference' + '-d' in 'cp'. -`no-inserted' - `-2' in `wdiff'. +'no-inserted' + '-2' in 'wdiff'. -`no-keep-going' - `-S' in `make'. +'no-keep-going' + '-S' in 'make'. -`no-lines' - `-l' in Bison. +'no-lines' + '-l' in Bison. -`no-piping' - `-P' in `shar'. +'no-piping' + '-P' in 'shar'. -`no-prof' - `-e' in `gprof'. +'no-prof' + '-e' in 'gprof'. -`no-regex' - `-R' in `etags'. +'no-regex' + '-R' in 'etags'. -`no-sort' - `-p' in `nm'. +'no-sort' + '-p' in 'nm'. -`no-splash' +'no-splash' Don't print a startup splash screen. -`no-split' - Used in `makeinfo'. +'no-split' + Used in 'makeinfo'. -`no-static' - `-a' in `gprof'. +'no-static' + '-a' in 'gprof'. -`no-time' - `-E' in `gprof'. +'no-time' + '-E' in 'gprof'. -`no-timestamp' - `-m' in `shar'. +'no-timestamp' + '-m' in 'shar'. -`no-validate' - Used in `makeinfo'. +'no-validate' + Used in 'makeinfo'. -`no-wait' - Used in `emacsclient'. +'no-wait' + Used in 'emacsclient'. -`no-warn' +'no-warn' Used in various programs to inhibit warnings. -`node' - `-n' in `info'. +'node' + '-n' in 'info'. -`nodename' - `-n' in `uname'. +'nodename' + '-n' in 'uname'. -`nonmatching' - `-f' in `cpio'. +'nonmatching' + '-f' in 'cpio'. -`nstuff' - `-n' in `objdump'. +'nstuff' + '-n' in 'objdump'. -`null' - `-0' in `xargs'. +'null' + '-0' in 'xargs'. -`number' - `-n' in `cat'. +'number' + '-n' in 'cat'. -`number-nonblank' - `-b' in `cat'. +'number-nonblank' + '-b' in 'cat'. -`numeric-sort' - `-n' in `nm'. +'numeric-sort' + '-n' in 'nm'. -`numeric-uid-gid' - `-n' in `cpio' and `ls'. +'numeric-uid-gid' + '-n' in 'cpio' and 'ls'. -`nx' +'nx' Used in GDB. -`old-archive' - `-o' in `tar'. +'old-archive' + '-o' in 'tar'. -`old-file' - `-o' in `make'. +'old-file' + '-o' in 'make'. -`one-file-system' - `-l' in `tar', `cp', and `du'. +'one-file-system' + '-l' in 'tar', 'cp', and 'du'. -`only-file' - `-o' in `ptx'. +'only-file' + '-o' in 'ptx'. -`only-prof' - `-f' in `gprof'. +'only-prof' + '-f' in 'gprof'. -`only-time' - `-F' in `gprof'. +'only-time' + '-F' in 'gprof'. -`options' - `-o' in `getopt', `fdlist', `fdmount', `fdmountd', and `fdumount'. +'options' + '-o' in 'getopt', 'fdlist', 'fdmount', 'fdmountd', and 'fdumount'. -`output' +'output' In various programs, specify the output file name. -`output-prefix' - `-o' in `shar'. +'output-prefix' + '-o' in 'shar'. -`override' - `-o' in `rm'. +'override' + '-o' in 'rm'. -`overwrite' - `-c' in `unshar'. +'overwrite' + '-c' in 'unshar'. -`owner' - `-o' in `install'. +'owner' + '-o' in 'install'. -`paginate' - `-l' in `diff'. +'paginate' + '-l' in 'diff'. -`paragraph-indent' - Used in `makeinfo'. +'paragraph-indent' + Used in 'makeinfo'. -`parents' - `-p' in `mkdir' and `rmdir'. +'parents' + '-p' in 'mkdir' and 'rmdir'. -`pass-all' - `-p' in `ul'. +'pass-all' + '-p' in 'ul'. -`pass-through' - `-p' in `cpio'. +'pass-through' + '-p' in 'cpio'. -`port' - `-P' in `finger'. +'port' + '-P' in 'finger'. -`portability' - `-c' in `cpio' and `tar'. +'portability' + '-c' in 'cpio' and 'tar'. -`posix' - Used in `gawk'. +'posix' + Used in 'gawk'. -`prefix-builtins' - `-P' in `m4'. +'prefix-builtins' + '-P' in 'm4'. -`prefix' - `-f' in `csplit'. +'prefix' + '-f' in 'csplit'. -`preserve' - Used in `tar' and `cp'. +'preserve' + Used in 'tar' and 'cp'. -`preserve-environment' - `-p' in `su'. +'preserve-environment' + '-p' in 'su'. -`preserve-modification-time' - `-m' in `cpio'. +'preserve-modification-time' + '-m' in 'cpio'. -`preserve-order' - `-s' in `tar'. +'preserve-order' + '-s' in 'tar'. -`preserve-permissions' - `-p' in `tar'. +'preserve-permissions' + '-p' in 'tar'. -`print' - `-l' in `diff'. +'print' + '-l' in 'diff'. -`print-chars' - `-L' in `cmp'. +'print-chars' + '-L' in 'cmp'. -`print-data-base' - `-p' in `make'. +'print-data-base' + '-p' in 'make'. -`print-directory' - `-w' in `make'. +'print-directory' + '-w' in 'make'. -`print-file-name' - `-o' in `nm'. +'print-file-name' + '-o' in 'nm'. -`print-symdefs' - `-s' in `nm'. +'print-symdefs' + '-s' in 'nm'. -`printer' - `-p' in `wdiff'. +'printer' + '-p' in 'wdiff'. -`prompt' - `-p' in `ed'. +'prompt' + '-p' in 'ed'. -`proxy' +'proxy' Specify an HTTP proxy. -`query-user' - `-X' in `shar'. +'query-user' + '-X' in 'shar'. -`question' - `-q' in `make'. +'question' + '-q' in 'make'. -`quiet' +'quiet' Used in many programs to inhibit the usual output. Every program - accepting `--quiet' should accept `--silent' as a synonym. + accepting '--quiet' should accept '--silent' as a synonym. -`quiet-unshar' - `-Q' in `shar' +'quiet-unshar' + '-Q' in 'shar' -`quote-name' - `-Q' in `ls'. +'quote-name' + '-Q' in 'ls'. -`rcs' - `-n' in `diff'. +'rcs' + '-n' in 'diff'. -`re-interval' - Used in `gawk'. +'re-interval' + Used in 'gawk'. -`read-full-blocks' - `-B' in `tar'. +'read-full-blocks' + '-B' in 'tar'. -`readnow' +'readnow' Used in GDB. -`recon' - `-n' in `make'. +'recon' + '-n' in 'make'. -`record-number' - `-R' in `tar'. +'record-number' + '-R' in 'tar'. -`recursive' - Used in `chgrp', `chown', `cp', `ls', `diff', and `rm'. +'recursive' + Used in 'chgrp', 'chown', 'cp', 'ls', 'diff', and 'rm'. -`reference' - `-r' in `touch'. +'reference' + '-r' in 'touch'. -`references' - `-r' in `ptx'. +'references' + '-r' in 'ptx'. -`regex' - `-r' in `tac' and `etags'. +'regex' + '-r' in 'tac' and 'etags'. -`release' - `-r' in `uname'. +'release' + '-r' in 'uname'. -`reload-state' - `-R' in `m4'. +'reload-state' + '-R' in 'm4'. -`relocation' - `-r' in `objdump'. +'relocation' + '-r' in 'objdump'. -`rename' - `-r' in `cpio'. +'rename' + '-r' in 'cpio'. -`replace' - `-i' in `xargs'. +'replace' + '-i' in 'xargs'. -`report-identical-files' - `-s' in `diff'. +'report-identical-files' + '-s' in 'diff'. -`reset-access-time' - `-a' in `cpio'. +'reset-access-time' + '-a' in 'cpio'. -`reverse' - `-r' in `ls' and `nm'. +'reverse' + '-r' in 'ls' and 'nm'. -`reversed-ed' - `-f' in `diff'. +'reversed-ed' + '-f' in 'diff'. -`right-side-defs' - `-R' in `ptx'. +'right-side-defs' + '-R' in 'ptx'. -`same-order' - `-s' in `tar'. +'same-order' + '-s' in 'tar'. -`same-permissions' - `-p' in `tar'. +'same-permissions' + '-p' in 'tar'. -`save' - `-g' in `stty'. +'save' + '-g' in 'stty'. -`se' +'se' Used in GDB. -`sentence-regexp' - `-S' in `ptx'. +'sentence-regexp' + '-S' in 'ptx'. -`separate-dirs' - `-S' in `du'. +'separate-dirs' + '-S' in 'du'. -`separator' - `-s' in `tac'. +'separator' + '-s' in 'tac'. -`sequence' - Used by `recode' to chose files or pipes for sequencing passes. +'sequence' + Used by 'recode' to chose files or pipes for sequencing passes. -`shell' - `-s' in `su'. +'shell' + '-s' in 'su'. -`show-all' - `-A' in `cat'. +'show-all' + '-A' in 'cat'. -`show-c-function' - `-p' in `diff'. +'show-c-function' + '-p' in 'diff'. -`show-ends' - `-E' in `cat'. +'show-ends' + '-E' in 'cat'. -`show-function-line' - `-F' in `diff'. +'show-function-line' + '-F' in 'diff'. -`show-tabs' - `-T' in `cat'. +'show-tabs' + '-T' in 'cat'. -`silent' +'silent' Used in many programs to inhibit the usual output. Every program - accepting `--silent' should accept `--quiet' as a synonym. + accepting '--silent' should accept '--quiet' as a synonym. -`size' - `-s' in `ls'. +'size' + '-s' in 'ls'. -`socket' +'socket' Specify a file descriptor for a network server to use for its - socket, instead of opening and binding a new socket. This - provides a way to run, in a non-privileged process, a server that - normally needs a reserved port number. + socket, instead of opening and binding a new socket. This provides + a way to run, in a non-privileged process, a server that normally + needs a reserved port number. -`sort' - Used in `ls'. +'sort' + Used in 'ls'. -`source' - `-W source' in `gawk'. +'source' + '-W source' in 'gawk'. -`sparse' - `-S' in `tar'. +'sparse' + '-S' in 'tar'. -`speed-large-files' - `-H' in `diff'. +'speed-large-files' + '-H' in 'diff'. -`split-at' - `-E' in `unshar'. +'split-at' + '-E' in 'unshar'. -`split-size-limit' - `-L' in `shar'. +'split-size-limit' + '-L' in 'shar'. -`squeeze-blank' - `-s' in `cat'. +'squeeze-blank' + '-s' in 'cat'. -`start-delete' - `-w' in `wdiff'. +'start-delete' + '-w' in 'wdiff'. -`start-insert' - `-y' in `wdiff'. +'start-insert' + '-y' in 'wdiff'. -`starting-file' - Used in `tar' and `diff' to specify which file within a directory +'starting-file' + Used in 'tar' and 'diff' to specify which file within a directory to start processing with. -`statistics' - `-s' in `wdiff'. +'statistics' + '-s' in 'wdiff'. -`stdin-file-list' - `-S' in `shar'. +'stdin-file-list' + '-S' in 'shar'. -`stop' - `-S' in `make'. +'stop' + '-S' in 'make'. -`strict' - `-s' in `recode'. +'strict' + '-s' in 'recode'. -`strip' - `-s' in `install'. +'strip' + '-s' in 'install'. -`strip-all' - `-s' in `strip'. +'strip-all' + '-s' in 'strip'. -`strip-debug' - `-S' in `strip'. +'strip-debug' + '-S' in 'strip'. -`submitter' - `-s' in `shar'. +'submitter' + '-s' in 'shar'. -`suffix' - `-S' in `cp', `ln', `mv'. +'suffix' + '-S' in 'cp', 'ln', 'mv'. -`suffix-format' - `-b' in `csplit'. +'suffix-format' + '-b' in 'csplit'. -`sum' - `-s' in `gprof'. +'sum' + '-s' in 'gprof'. -`summarize' - `-s' in `du'. +'summarize' + '-s' in 'du'. -`symbolic' - `-s' in `ln'. +'symbolic' + '-s' in 'ln'. -`symbols' - Used in GDB and `objdump'. +'symbols' + Used in GDB and 'objdump'. -`synclines' - `-s' in `m4'. +'synclines' + '-s' in 'm4'. -`sysname' - `-s' in `uname'. +'sysname' + '-s' in 'uname'. -`tabs' - `-t' in `expand' and `unexpand'. +'tabs' + '-t' in 'expand' and 'unexpand'. -`tabsize' - `-T' in `ls'. +'tabsize' + '-T' in 'ls'. -`terminal' - `-T' in `tput' and `ul'. `-t' in `wdiff'. +'terminal' + '-T' in 'tput' and 'ul'. '-t' in 'wdiff'. -`text' - `-a' in `diff'. +'text' + '-a' in 'diff'. -`text-files' - `-T' in `shar'. +'text-files' + '-T' in 'shar'. -`time' - Used in `ls' and `touch'. +'time' + Used in 'ls' and 'touch'. -`timeout' +'timeout' Specify how long to wait before giving up on some operation. -`to-stdout' - `-O' in `tar'. +'to-stdout' + '-O' in 'tar'. -`total' - `-c' in `du'. +'total' + '-c' in 'du'. -`touch' - `-t' in `make', `ranlib', and `recode'. +'touch' + '-t' in 'make', 'ranlib', and 'recode'. -`trace' - `-t' in `m4'. +'trace' + '-t' in 'm4'. -`traditional' - `-t' in `hello'; `-W traditional' in `gawk'; `-G' in `ed', `m4', - and `ptx'. +'traditional' + '-t' in 'hello'; '-W traditional' in 'gawk'; '-G' in 'ed', 'm4', + and 'ptx'. -`tty' +'tty' Used in GDB. -`typedefs' - `-t' in `ctags'. +'typedefs' + '-t' in 'ctags'. -`typedefs-and-c++' - `-T' in `ctags'. +'typedefs-and-c++' + '-T' in 'ctags'. -`typeset-mode' - `-t' in `ptx'. +'typeset-mode' + '-t' in 'ptx'. -`uncompress' - `-z' in `tar'. +'uncompress' + '-z' in 'tar'. -`unconditional' - `-u' in `cpio'. +'unconditional' + '-u' in 'cpio'. -`undefine' - `-U' in `m4'. +'undefine' + '-U' in 'm4'. -`undefined-only' - `-u' in `nm'. +'undefined-only' + '-u' in 'nm'. -`update' - `-u' in `cp', `ctags', `mv', `tar'. +'update' + '-u' in 'cp', 'ctags', 'mv', 'tar'. -`usage' - Used in `gawk'; same as `--help'. +'usage' + Used in 'gawk'; same as '--help'. -`uuencode' - `-B' in `shar'. +'uuencode' + '-B' in 'shar'. -`vanilla-operation' - `-V' in `shar'. +'vanilla-operation' + '-V' in 'shar'. -`verbose' +'verbose' Print more information about progress. Many programs support this. -`verify' - `-W' in `tar'. +'verify' + '-W' in 'tar'. -`version' +'version' Print the version number. -`version-control' - `-V' in `cp', `ln', `mv'. +'version-control' + '-V' in 'cp', 'ln', 'mv'. -`vgrind' - `-v' in `ctags'. +'vgrind' + '-v' in 'ctags'. -`volume' - `-V' in `tar'. +'volume' + '-V' in 'tar'. -`what-if' - `-W' in `make'. +'what-if' + '-W' in 'make'. -`whole-size-limit' - `-l' in `shar'. +'whole-size-limit' + '-l' in 'shar'. -`width' - `-w' in `ls' and `ptx'. +'width' + '-w' in 'ls' and 'ptx'. -`word-regexp' - `-W' in `ptx'. +'word-regexp' + '-W' in 'ptx'. -`writable' - `-T' in `who'. +'writable' + '-T' in 'who'. -`zeros' - `-z' in `gprof'. +'zeros' + '-z' in 'gprof'. File: standards.info, Node: OID Allocations, Next: Memory Usage, Prev: Option Table, Up: Program Behavior @@ -2122,7 +2116,7 @@ File: standards.info, Node: OID Allocations, Next: Memory Usage, Prev: Option The OID (object identifier) 1.3.6.1.4.1.11591 has been assigned to the GNU Project (thanks to Werner Koch). These are used for SNMP, LDAP, X.509 certificates, and so on. The web site -`http://www.alvestrand.no/objectid' has a (voluntary) listing of many +<http://www.alvestrand.no/objectid> has a (voluntary) listing of many OID assignments. If you need a new slot for your GNU package, write @@ -2175,10 +2169,10 @@ File: standards.info, Node: Memory Usage, Next: File Usage, Prev: OID Allocat If a program typically uses just a few meg of memory, don't bother making any effort to reduce memory usage. For example, if it is impractical for other reasons to operate on files more than a few meg -long, it is reasonable to read entire input files into memory to -operate on them. +long, it is reasonable to read entire input files into memory to operate +on them. - However, for programs such as `cat' or `tail', that can usefully + However, for programs such as 'cat' or 'tail', that can usefully operate on very large files, it is important to avoid using a technique that would artificially limit the size of files it can handle. If a program works by lines and could be applied to arbitrary user-supplied @@ -2187,7 +2181,7 @@ very hard and users will want to be able to operate on input files that are bigger than will fit in memory all at once. If your program creates complicated data structures, just make them -in memory and give a fatal error if `malloc' returns zero. +in memory and give a fatal error if 'malloc' returns zero. File: standards.info, Node: File Usage, Prev: Memory Usage, Up: Program Behavior @@ -2195,15 +2189,15 @@ File: standards.info, Node: File Usage, Prev: Memory Usage, Up: Program Behav 4.11 File Usage =============== -Programs should be prepared to operate when `/usr' and `/etc' are +Programs should be prepared to operate when '/usr' and '/etc' are read-only file systems. Thus, if the program manages log files, lock files, backup files, score files, or any other files which are modified -for internal purposes, these files should not be stored in `/usr' or -`/etc'. +for internal purposes, these files should not be stored in '/usr' or +'/etc'. - There are two exceptions. `/etc' is used to store system + There are two exceptions. '/etc' is used to store system configuration information; it is reasonable for a program to modify -files in `/etc' when its job is to update the system configuration. +files in '/etc' when its job is to update the system configuration. Also, if the user explicitly asks to modify one file in a directory, it is reasonable for the program to store other files in the same directory. @@ -2225,11 +2219,11 @@ writing GNU software. * Names:: Naming variables, functions, and files. * System Portability:: Portability among different operating systems. * CPU Portability:: Supporting the range of CPU types. -* System Functions:: Portability and ``standard'' library functions. +* System Functions:: Portability and "standard" library functions. * Internationalization:: Techniques for internationalization. * Character Set:: Use ASCII by default. -* Quote Characters:: Use `...' in the C locale. -* Mmap:: How you can safely use `mmap'. +* Quote Characters:: Use '...' in the C locale. +* Mmap:: How you can safely use 'mmap'. File: standards.info, Node: Formatting, Next: Comments, Up: Writing C @@ -2244,7 +2238,7 @@ functions. These tools will not work on code not formatted that way. Avoid putting open-brace, open-parenthesis or open-bracket in column one when they are inside a function, so that they won't start a defun. -The open-brace that starts a `struct' body can go in column one if you +The open-brace that starts a 'struct' body can go in column one if you find it useful to treat that definition as a defun. It is also important for function definitions to start the name of @@ -2277,7 +2271,7 @@ it like this: ... The rest of this section gives our recommendations for other aspects -of C formatting style, which is also the default style of the `indent' +of C formatting style, which is also the default style of the 'indent' program in version 1.2 and newer. It corresponds to the options -nbad -bap -nbc -bbo -bl -bli2 -bls -ncdb -nce -cp1 -cs -di2 @@ -2361,31 +2355,31 @@ File: standards.info, Node: Comments, Next: Syntactic Conventions, Prev: Form ======================== Every program should start with a comment saying briefly what it is for. -Example: `fmt - filter for simple filling of text'. This comment -should be at the top of the source file containing the `main' function -of the program. +Example: 'fmt - filter for simple filling of text'. This comment should +be at the top of the source file containing the 'main' function of the +program. Also, please write a brief comment at the start of each source file, with the file name and a line or two about the overall purpose of the file. Please write the comments in a GNU program in English, because -English is the one language that nearly all programmers in all -countries can read. If you do not write English well, please write -comments in English as well as you can, then ask other people to help -rewrite them. If you can't write comments in English, please find -someone to work with you and translate your comments into English. +English is the one language that nearly all programmers in all countries +can read. If you do not write English well, please write comments in +English as well as you can, then ask other people to help rewrite them. +If you can't write comments in English, please find someone to work with +you and translate your comments into English. Please put a comment on each function saying what the function does, what sorts of arguments it gets, and what the possible values of arguments mean and are used for. It is not necessary to duplicate in words the meaning of the C argument declarations, if a C type is being used in its customary fashion. If there is anything nonstandard about -its use (such as an argument of type `char *' which is really the +its use (such as an argument of type 'char *' which is really the address of the second character of a string, not the first), or any possible values that would not work the way one would expect (such as, -that strings containing newlines are not guaranteed to work), be sure -to say so. +that strings containing newlines are not guaranteed to work), be sure to +say so. Also explain the significance of the return value, if there is one. @@ -2414,10 +2408,10 @@ function itself would be off the bottom of the screen. zero means continue them. */ int truncate_lines; - Every `#endif' should have a comment, except in the case of short + Every '#endif' should have a comment, except in the case of short conditionals (just a few lines) that are not nested. The comment should state the condition of the conditional that is ending, _including its -sense_. `#else' should have a comment describing the condition _and +sense_. '#else' should have a comment describing the condition _and sense_ of the code that follows. For example: #ifdef foo @@ -2429,7 +2423,7 @@ sense_ of the code that follows. For example: ... #endif /* foo */ -but, by contrast, write the comments this way for a `#ifndef': +but, by contrast, write the comments this way for a '#ifndef': #ifndef foo ... @@ -2448,23 +2442,23 @@ File: standards.info, Node: Syntactic Conventions, Next: Names, Prev: Comment Please explicitly declare the types of all objects. For example, you should explicitly declare all arguments to functions, and you should -declare functions to return `int' rather than omitting the `int'. +declare functions to return 'int' rather than omitting the 'int'. - Some programmers like to use the GCC `-Wall' option, and change the + Some programmers like to use the GCC '-Wall' option, and change the code whenever it issues a warning. If you want to do this, then do. -Other programmers prefer not to use `-Wall', because it gives warnings +Other programmers prefer not to use '-Wall', because it gives warnings for valid and legitimate code which they do not want to change. If you -want to do this, then do. The compiler should be your servant, not -your master. +want to do this, then do. The compiler should be your servant, not your +master. Declarations of external functions and functions to appear later in the source file should all go in one place near the beginning of the file (somewhere before the first function definition in the file), or -else should go in a header file. Don't put `extern' declarations inside +else should go in a header file. Don't put 'extern' declarations inside functions. It used to be common practice to use the same local variables (with -names like `tem') over and over for different values within one +names like 'tem') over and over for different values within one function. Instead of doing this, it is better to declare a separate local variable for each distinct purpose, and give it a name which is meaningful. This not only makes programs easier to understand, it also @@ -2494,8 +2488,8 @@ or this: (If they are global variables, each should have a comment preceding it anyway.) - When you have an `if'-`else' statement nested in another `if' -statement, always put braces around the `if'-`else'. Thus, never write + When you have an 'if'-'else' statement nested in another 'if' +statement, always put braces around the 'if'-'else'. Thus, never write like this: if (foo) @@ -2514,16 +2508,16 @@ always like this: lose (); } - If you have an `if' statement nested inside of an `else' statement, -either write `else if' on one line, like this, + If you have an 'if' statement nested inside of an 'else' statement, +either write 'else if' on one line, like this, if (foo) ... else if (bar) ... -with its `then'-part indented like the preceding `then'-part, or write -the nested `if' within braces like this: +with its 'then'-part indented like the preceding 'then'-part, or write +the nested 'if' within braces like this: if (foo) ... @@ -2537,8 +2531,8 @@ the nested `if' within braces like this: same declaration. Instead, declare the structure tag separately and then use it to declare the variables or typedefs. - Try to avoid assignments inside `if'-conditions (assignments inside -`while'-conditions are ok). For example, don't write this: + Try to avoid assignments inside 'if'-conditions (assignments inside +'while'-conditions are ok). For example, don't write this: if ((foo = (char *) malloc (sizeof *foo)) == 0) fatal ("virtual memory exhausted"); @@ -2549,8 +2543,8 @@ instead, write this: if (foo == 0) fatal ("virtual memory exhausted"); - Don't make the program ugly to placate `lint'. Please don't insert -any casts to `void'. Zero without a cast is perfectly fine as a null + Don't make the program ugly to placate 'lint'. Please don't insert +any casts to 'void'. Zero without a cast is perfectly fine as a null pointer constant, except when calling a varargs function. @@ -2574,32 +2568,32 @@ frequently, but don't use lots of obscure abbreviations. Please use underscores to separate words in a name, so that the Emacs word commands can be useful within them. Stick to lower case; reserve -upper case for macros and `enum' constants, and for name-prefixes that +upper case for macros and 'enum' constants, and for name-prefixes that follow a uniform convention. - For example, you should use names like `ignore_space_change_flag'; -don't use names like `iCantReadThis'. + For example, you should use names like 'ignore_space_change_flag'; +don't use names like 'iCantReadThis'. Variables that indicate whether command-line options have been -specified should be named after the meaning of the option, not after -the option-letter. A comment should state both the exact meaning of -the option and its letter. For example, +specified should be named after the meaning of the option, not after the +option-letter. A comment should state both the exact meaning of the +option and its letter. For example, /* Ignore changes in horizontal whitespace (-b). */ int ignore_space_change_flag; When you want to define names with constant integer values, use -`enum' rather than `#define'. GDB knows about enumeration constants. +'enum' rather than '#define'. GDB knows about enumeration constants. You might want to make sure that none of the file names would conflict if the files were loaded onto an MS-DOS file system which -shortens the names. You can use the program `doschk' to test for this. +shortens the names. You can use the program 'doschk' to test for this. Some GNU programs were designed to limit themselves to file names of 14 characters or less, to avoid file name conflicts if they are read into older System V systems. Please preserve this feature in the existing GNU programs that have it, but there is no need to do this in -new GNU programs. `doschk' also reports file names longer than 14 +new GNU programs. 'doschk' also reports file names longer than 14 characters. @@ -2632,7 +2626,7 @@ because most of the programs that need such knowledge have already been written. Avoid using the format of semi-internal data bases (e.g., -directories) when there is a higher-level alternative (`readdir'). +directories) when there is a higher-level alternative ('readdir'). As for systems that are not like Unix, such as MSDOS, Windows, VMS, MVS, and older Macintosh systems, supporting them is often a lot of @@ -2643,19 +2637,18 @@ supporting other incompatible systems. If you do support Windows, please do not abbreviate it as "win". In hacker terminology, calling something a "win" is a form of praise. You're free to praise Microsoft Windows on your own if you want, but -please don't do this in GNU packages. Instead of abbreviating -"Windows" to "win", you can write it in full or abbreviate it to "woe" -or "w". In GNU Emacs, for instance, we use `w32' in file names of -Windows-specific files, but the macro for Windows conditionals is -called `WINDOWSNT'. - - It is a good idea to define the "feature test macro" `_GNU_SOURCE' -when compiling your C files. When you compile on GNU or GNU/Linux, -this will enable the declarations of GNU library extension functions, -and that will usually give you a compiler error message if you define -the same function names in some other way in your program. (You don't -have to actually _use_ these functions, if you prefer to make the -program more portable to other systems.) +please don't do this in GNU packages. Instead of abbreviating "Windows" +to "win", you can write it in full or abbreviate it to "woe" or "w". In +GNU Emacs, for instance, we use 'w32' in file names of Windows-specific +files, but the macro for Windows conditionals is called 'WINDOWSNT'. + + It is a good idea to define the "feature test macro" '_GNU_SOURCE' +when compiling your C files. When you compile on GNU or GNU/Linux, this +will enable the declarations of GNU library extension functions, and +that will usually give you a compiler error message if you define the +same function names in some other way in your program. (You don't have +to actually _use_ these functions, if you prefer to make the program +more portable to other systems.) But whether or not you use these GNU extensions, you should avoid using their names for any other meanings. Doing so would make it hard @@ -2667,15 +2660,14 @@ File: standards.info, Node: CPU Portability, Next: System Functions, Prev: Sy 5.6 Portability between CPUs ============================ -Even GNU systems will differ because of differences among CPU -types--for example, difference in byte ordering and alignment -requirements. It is absolutely essential to handle these differences. -However, don't make any effort to cater to the possibility that an -`int' will be less than 32 bits. We don't support 16-bit machines in -GNU. +Even GNU systems will differ because of differences among CPU types--for +example, difference in byte ordering and alignment requirements. It is +absolutely essential to handle these differences. However, don't make +any effort to cater to the possibility that an 'int' will be less than +32 bits. We don't support 16-bit machines in GNU. Similarly, don't make any effort to cater to the possibility that -`long' will be smaller than predefined types like `size_t'. For +'long' will be smaller than predefined types like 'size_t'. For example, the following code is ok: printf ("size = %lu\n", (unsigned long) sizeof array); @@ -2683,15 +2675,15 @@ example, the following code is ok: 1989 Standard C requires this to work, and we know of only one counterexample: 64-bit programs on Microsoft Windows. We will leave it -to those who want to port GNU programs to that environment to figure -out how to do it. +to those who want to port GNU programs to that environment to figure out +how to do it. - Predefined file-size types like `off_t' are an exception: they are -longer than `long' on many platforms, so code like the above won't work -with them. One way to print an `off_t' value portably is to print its + Predefined file-size types like 'off_t' are an exception: they are +longer than 'long' on many platforms, so code like the above won't work +with them. One way to print an 'off_t' value portably is to print its digits yourself, one by one. - Don't assume that the address of an `int' object is also the address + Don't assume that the address of an 'int' object is also the address of its least-significant byte. This is false on big-endian machines. Thus, don't make the following mistake: @@ -2700,9 +2692,9 @@ Thus, don't make the following mistake: while ((c = getchar ()) != EOF) write (file_descriptor, &c, 1); -Instead, use `unsigned char' as follows. (The `unsigned' is for -portability to unusual systems where `char' is signed and where there -is integer overflow checking.) +Instead, use 'unsigned char' as follows. (The 'unsigned' is for +portability to unusual systems where 'char' is signed and where there is +integer overflow checking.) int c; while ((c = getchar ()) != EOF) @@ -2713,14 +2705,14 @@ is integer overflow checking.) It used to be ok to not worry about the difference between pointers and integers when passing arguments to functions. However, on most -modern 64-bit machines pointers are wider than `int'. Conversely, -integer types like `long long int' and `off_t' are wider than pointers -on most modern 32-bit machines. Hence it's often better nowadays to -use prototypes to define functions whose argument types are not trivial. +modern 64-bit machines pointers are wider than 'int'. Conversely, +integer types like 'long long int' and 'off_t' are wider than pointers +on most modern 32-bit machines. Hence it's often better nowadays to use +prototypes to define functions whose argument types are not trivial. In particular, if functions accept varying argument counts or types -they should be declared using prototypes containing `...' and defined -using `stdarg.h'. For an example of this, please see the Gnulib +they should be declared using prototypes containing '...' and defined +using 'stdarg.h'. For an example of this, please see the Gnulib (http://www.gnu.org/software/gnulib/) error module, which declares and defines the following function: @@ -2731,8 +2723,8 @@ defines the following function: void error (int status, int errnum, const char *format, ...); A simple way to use the Gnulib error module is to obtain the two -source files `error.c' and `error.h' from the Gnulib library source -code repository at `http://git.savannah.gnu.org/gitweb/?p=gnulib.git'. +source files 'error.c' and 'error.h' from the Gnulib library source code +repository at <http://git.savannah.gnu.org/gitweb/?p=gnulib.git>. Here's a sample use: #include "error.h" @@ -2756,8 +2748,8 @@ cases where casting pointers to integers is essential--such as, a Lisp interpreter which stores type information as well as an address in one word--you'll have to make explicit provisions to handle different word sizes. You will also need to make provision for systems in which the -normal range of addresses you can get from `malloc' starts far away -from zero. +normal range of addresses you can get from 'malloc' starts far away from +zero. File: standards.info, Node: System Functions, Next: Internationalization, Prev: CPU Portability, Up: Writing C @@ -2765,57 +2757,56 @@ File: standards.info, Node: System Functions, Next: Internationalization, Pre 5.7 Calling System Functions ============================ -C implementations differ substantially. Standard C reduces but does -not eliminate the incompatibilities; meanwhile, many GNU packages still +C implementations differ substantially. Standard C reduces but does not +eliminate the incompatibilities; meanwhile, many GNU packages still support pre-standard compilers because this is not hard to do. This chapter gives recommendations for how to use the more-or-less standard C library functions to avoid unnecessary loss of portability. - * Don't use the return value of `sprintf'. It returns the number of + * Don't use the return value of 'sprintf'. It returns the number of characters written on some systems, but not on all systems. - * Be aware that `vfprintf' is not always available. + * Be aware that 'vfprintf' is not always available. - * `main' should be declared to return type `int'. It should - terminate either by calling `exit' or by returning the integer + * 'main' should be declared to return type 'int'. It should + terminate either by calling 'exit' or by returning the integer status code; make sure it cannot ever return an undefined value. * Don't declare system functions explicitly. Almost any declaration for a system function is wrong on some - system. To minimize conflicts, leave it to the system header - files to declare system functions. If the headers don't declare a + system. To minimize conflicts, leave it to the system header files + to declare system functions. If the headers don't declare a function, let it remain undeclared. While it may seem unclean to use a function without declaring it, in practice this works fine for most system library functions on the systems where this really happens; thus, the disadvantage is - only theoretical. By contrast, actual declarations have - frequently caused actual conflicts. + only theoretical. By contrast, actual declarations have frequently + caused actual conflicts. * If you must declare a system function, don't specify the argument types. Use an old-style declaration, not a Standard C prototype. The more you specify about the function, the more likely a conflict. - * In particular, don't unconditionally declare `malloc' or `realloc'. + * In particular, don't unconditionally declare 'malloc' or 'realloc'. Most GNU programs use those functions just once, in functions - conventionally named `xmalloc' and `xrealloc'. These functions - call `malloc' and `realloc', respectively, and check the results. + conventionally named 'xmalloc' and 'xrealloc'. These functions + call 'malloc' and 'realloc', respectively, and check the results. - Because `xmalloc' and `xrealloc' are defined in your program, you + Because 'xmalloc' and 'xrealloc' are defined in your program, you can declare them in other files without any risk of type conflict. - On most systems, `int' is the same length as a pointer; thus, the - calls to `malloc' and `realloc' work fine. For the few - exceptional systems (mostly 64-bit machines), you can use - *conditionalized* declarations of `malloc' and `realloc'--or put - these declarations in configuration files specific to those - systems. + On most systems, 'int' is the same length as a pointer; thus, the + calls to 'malloc' and 'realloc' work fine. For the few exceptional + systems (mostly 64-bit machines), you can use *conditionalized* + declarations of 'malloc' and 'realloc'--or put these declarations + in configuration files specific to those systems. * The string functions require special treatment. Some Unix systems - have a header file `string.h'; others have `strings.h'. Neither + have a header file 'string.h'; others have 'strings.h'. Neither file name is portable. There are two things you can do: use Autoconf to figure out which file to include, or don't include either file. @@ -2826,8 +2817,8 @@ library functions to avoid unnecessary loss of portability. That causes less of a problem than you might think. The newer standard string functions should be avoided anyway because many - systems still don't support them. The string functions you can - use are these: + systems still don't support them. The string functions you can use + are these: strcpy strncpy strcat strncat strlen strcmp strncmp @@ -2835,30 +2826,30 @@ library functions to avoid unnecessary loss of portability. The copy and concatenate functions work fine without a declaration as long as you don't use their values. Using their values without - a declaration fails on systems where the width of a pointer - differs from the width of `int', and perhaps in other cases. It - is trivial to avoid using their values, so do that. + a declaration fails on systems where the width of a pointer differs + from the width of 'int', and perhaps in other cases. It is trivial + to avoid using their values, so do that. - The compare functions and `strlen' work fine without a declaration + The compare functions and 'strlen' work fine without a declaration on most systems, possibly all the ones that GNU software runs on. You may find it necessary to declare them *conditionally* on a few systems. - The search functions must be declared to return `char *'. Luckily, + The search functions must be declared to return 'char *'. Luckily, there is no variation in the data type they return. But there is variation in their names. Some systems give these functions the - names `index' and `rindex'; other systems use the names `strchr' - and `strrchr'. Some systems support both pairs of names, but + names 'index' and 'rindex'; other systems use the names 'strchr' + and 'strrchr'. Some systems support both pairs of names, but neither pair works on all systems. You should pick a single pair of names and use it throughout your - program. (Nowadays, it is better to choose `strchr' and `strrchr' + program. (Nowadays, it is better to choose 'strchr' and 'strrchr' for new programs, since those are the standard names.) Declare - both of those names as functions returning `char *'. On systems + both of those names as functions returning 'char *'. On systems which don't support those names, define them as macros in terms of the other pair. For example, here is what to put at the beginning - of your file (or in a header) if you want to use the names - `strchr' and `strrchr' throughout: + of your file (or in a header) if you want to use the names 'strchr' + and 'strrchr' throughout: #ifndef HAVE_STRCHR #define strchr index @@ -2870,7 +2861,7 @@ library functions to avoid unnecessary loss of portability. char *strchr (); char *strrchr (); - Here we assume that `HAVE_STRCHR' and `HAVE_STRRCHR' are macros + Here we assume that 'HAVE_STRCHR' and 'HAVE_STRRCHR' are macros defined in systems where the corresponding functions exist. One way to get them properly defined is to use Autoconf. @@ -2886,22 +2877,22 @@ library in every program. Use English for the messages as they appear in the program, and let gettext provide the way to translate them into other languages. - Using GNU gettext involves putting a call to the `gettext' macro + Using GNU gettext involves putting a call to the 'gettext' macro around each string that might need translation--like this: printf (gettext ("Processing file `%s'...")); -This permits GNU gettext to replace the string `"Processing file +This permits GNU gettext to replace the string '"Processing file `%s'..."' with a translated version. Once a program uses gettext, please make a point of writing calls to -`gettext' when you add new strings that call for translation. +'gettext' when you add new strings that call for translation. Using GNU gettext in a package involves specifying a "text domain name" for the package. The text domain name is used to separate the translations for this package from the translations for other packages. Normally, the text domain name should be the same as the name of the -package--for example, `coreutils' for the GNU core utilities. +package--for example, 'coreutils' for the GNU core utilities. To enable gettext to work well, avoid writing code that makes assumptions about the structure of words or sentences. When you want @@ -2936,9 +2927,9 @@ this code: printf ("# Implicit rule search has%s been done.\n", f->tried_implicit ? "" : " not"); -Adding `gettext' calls to this code cannot give correct results for all +Adding 'gettext' calls to this code cannot give correct results for all languages, because negation in some languages requires adding words at -more than one place in the sentence. By contrast, adding `gettext' +more than one place in the sentence. By contrast, adding 'gettext' calls does the job straightforwardly if the code starts out like this: printf (f->tried_implicit @@ -2951,13 +2942,13 @@ calls does the job straightforwardly if the code starts out like this: nfiles != 1 ? "s" : ""); The problem with this example is that it assumes that plurals are made -by adding `s'. If you apply gettext to the format string, like this, +by adding 's'. If you apply gettext to the format string, like this, printf (gettext ("%d file%s processed"), nfiles, nfiles != 1 ? "s" : ""); the message can use different words, but it will still be forced to use -`s' for the plural. Here is a better way, with gettext being applied to +'s' for the plural. Here is a better way, with gettext being applied to the two strings independently: printf ((nfiles != 1 ? gettext ("%d files processed") @@ -2966,7 +2957,7 @@ the two strings independently: But this still doesn't work for languages like Polish, which has three plural forms: one for nfiles == 1, one for nfiles == 2, 3, 4, 22, 23, -24, ... and one for the rest. The GNU `ngettext' function solves this +24, ... and one for the rest. The GNU 'ngettext' function solves this problem: printf (ngettext ("%d files processed", "%d file processed", nfiles), @@ -2997,24 +2988,24 @@ File: standards.info, Node: Quote Characters, Next: Mmap, Prev: Character Set ===================== In the C locale, GNU programs should stick to plain ASCII for quotation -characters in messages to users: preferably 0x60 (``') for left quotes -and 0x27 (`'') for right quotes. It is ok, but not required, to use +characters in messages to users: preferably 0x60 ('`') for left quotes +and 0x27 (''') for right quotes. It is ok, but not required, to use locale-specific quotes in other locales. - The Gnulib (http://www.gnu.org/software/gnulib/) `quote' and -`quotearg' modules provide a reasonably straightforward way to support + The Gnulib (http://www.gnu.org/software/gnulib/) 'quote' and +'quotearg' modules provide a reasonably straightforward way to support locale-specific quote characters, as well as taking care of other issues, such as quoting a filename that itself contains a quote character. See the Gnulib documentation for usage details. In any case, the documentation for your program should clearly specify how it does quoting, if different than the preferred method of -``' and `''. This is especially important if the output of your -program is ever likely to be parsed by another program. +'`' and '''. This is especially important if the output of your program +is ever likely to be parsed by another program. Quotation characters are a difficult area in the computing world at this time: there are no true left or right quote characters in Latin1; -the ``' character we use was standardized there as a grave accent. +the '`' character we use was standardized there as a grave accent. Moreover, Latin1 is still not universally usable. Unicode contains the unambiguous quote characters required, and its @@ -3030,18 +3021,18 @@ File: standards.info, Node: Mmap, Prev: Quote Characters, Up: Writing C 5.11 Mmap ========= -Don't assume that `mmap' either works on all files or fails for all +Don't assume that 'mmap' either works on all files or fails for all files. It may work on some files and fail on others. - The proper way to use `mmap' is to try it on the specific file for -which you want to use it--and if `mmap' doesn't work, fall back on -doing the job in another way using `read' and `write'. + The proper way to use 'mmap' is to try it on the specific file for +which you want to use it--and if 'mmap' doesn't work, fall back on doing +the job in another way using 'read' and 'write'. The reason this precaution is needed is that the GNU kernel (the HURD) provides a user-extensible file system, in which there can be many -different kinds of "ordinary files." Many of them support `mmap', but -some do not. It is important to make programs handle all these kinds -of files. +different kinds of "ordinary files." Many of them support 'mmap', but +some do not. It is important to make programs handle all these kinds of +files. File: standards.info, Node: Documentation, Next: Managing Releases, Prev: Writing C, Up: Top @@ -3080,8 +3071,8 @@ documentation in Texinfo both for reference and for learners. Texinfo makes it possible to produce a good quality formatted book, using TeX, and to generate an Info file. It is also possible to generate HTML output from Texinfo source. See the Texinfo manual, either the -hardcopy, or the on-line version available through `info' or the Emacs -Info subsystem (`C-h i'). +hardcopy, or the on-line version available through 'info' or the Emacs +Info subsystem ('C-h i'). Nowadays some other formats such as Docbook and Sgmltexi can be converted automatically into Texinfo. It is ok to produce the Texinfo @@ -3105,8 +3096,8 @@ within the manual). Sometimes this structure of ideas matches the structure of the implementation of the software being documented--but often they are different. An important part of learning to write good documentation is to learn to notice when you have unthinkingly -structured the documentation like the implementation, stop yourself, -and look for better alternatives. +structured the documentation like the implementation, stop yourself, and +look for better alternatives. For example, each program in the GNU system probably ought to be documented in one manual; but this does not mean each program should @@ -3115,10 +3106,10 @@ implementation, rather than the structure that helps the user understand. Instead, each manual should cover a coherent _topic_. For example, -instead of a manual for `diff' and a manual for `diff3', we have one -manual for "comparison of files" which covers both of those programs, -as well as `cmp'. By documenting these programs together, we can make -the whole subject clearer. +instead of a manual for 'diff' and a manual for 'diff3', we have one +manual for "comparison of files" which covers both of those programs, as +well as 'cmp'. By documenting these programs together, we can make the +whole subject clearer. The manual which discusses a program should certainly document all of the program's command-line options and all of its commands. It should @@ -3171,13 +3162,13 @@ bugs _in the text of the manual_. documentation; use "file name" (two words) instead. We use the term "path" only for search paths, which are lists of directory names. - Please do not use the term "illegal" to refer to erroneous input to -a computer program. Please use "invalid" for this, and reserve the -term "illegal" for activities prohibited by law. + Please do not use the term "illegal" to refer to erroneous input to a +computer program. Please use "invalid" for this, and reserve the term +"illegal" for activities prohibited by law. - Please do not write `()' after a function name just to indicate it -is a function. `foo ()' is not a function, it is a function call with -no arguments. + Please do not write '()' after a function name just to indicate it is +a function. 'foo ()' is not a function, it is a function call with no +arguments. File: standards.info, Node: Doc Strings and Manuals, Next: Manual Structure Details, Prev: GNU Manuals, Up: Documentation @@ -3222,17 +3213,17 @@ frequently than or independent of the program, also state a version number for the manual in both of these places. Each program documented in the manual should have a node named -`PROGRAM Invocation' or `Invoking PROGRAM'. This node (together with +'PROGRAM Invocation' or 'Invoking PROGRAM'. This node (together with its subnodes, if any) should describe the program's command line arguments and how to run it (the sort of information people would look -for in a man page). Start with an `@example' containing a template for +for in a man page). Start with an '@example' containing a template for all the options and arguments that the program uses. Alternatively, put a menu item in some menu whose item name fits one of the above patterns. This identifies the node which that item points to as the node for this purpose, regardless of the node's actual name. - The `--usage' feature of the Info reader looks for such a node or + The '--usage' feature of the Info reader looks for such a node or menu item in order to find the relevant text, so it is essential for every Texinfo file to have one. @@ -3251,11 +3242,11 @@ documents--you only need one copy of the GNU FDL for the whole collection. For a single short document, you can use a very permissive non-copyleft license, to avoid taking up space with a long license. - See `http://www.gnu.org/copyleft/fdl-howto.html' for more explanation + See <http://www.gnu.org/copyleft/fdl-howto.html> for more explanation of how to employ the GFDL. Note that it is not obligatory to include a copy of the GNU GPL or -GNU LGPL in a manual whose license is neither the GPL nor the LGPL. It +GNU LGPL in a manual whose license is neither the GPL nor the LGPL. It can be a good idea to include the program's license in a large manual; in a short manual, whose size would be increased considerably by including the program's license, it is probably better not to include @@ -3282,7 +3273,7 @@ The FSF publishes some GNU manuals in printed form. To encourage sales of these manuals, the on-line versions of the manual should mention at the very start that the printed manual is available and should point at information for getting it--for instance, with a link to the page -`http://www.gnu.org/order/order.html'. This should not be included in +<http://www.gnu.org/order/order.html>. This should not be included in the printed manual, though, because there it is redundant. It is also useful to explain in the on-line forms of the manual how @@ -3294,15 +3285,15 @@ File: standards.info, Node: NEWS File, Next: Change Logs, Prev: Printed Manua 6.7 The NEWS File ================= -In addition to its manual, the package should have a file named `NEWS' -which contains a list of user-visible changes worth mentioning. In -each new release, add items to the front of the file and identify the -version they pertain to. Don't discard old items; leave them in the -file after the newer items. This way, a user upgrading from any -previous version can see what is new. +In addition to its manual, the package should have a file named 'NEWS' +which contains a list of user-visible changes worth mentioning. In each +new release, add items to the front of the file and identify the version +they pertain to. Don't discard old items; leave them in the file after +the newer items. This way, a user upgrading from any previous version +can see what is new. - If the `NEWS' file gets very long, move some of the older items into -a file named `ONEWS' and put a note at the end referring the user to + If the 'NEWS' file gets very long, move some of the older items into +a file named 'ONEWS' and put a note at the end referring the user to that file. @@ -3339,33 +3330,33 @@ People can see the current version; they don't need the change log to tell them what is in it. What they want from a change log is a clear explanation of how the earlier version differed. - The change log file is normally called `ChangeLog' and covers an + The change log file is normally called 'ChangeLog' and covers an entire directory. Each directory can have its own change log, or a directory can use the change log of its parent directory--it's up to you. Another alternative is to record change log information with a -version control system such as RCS or CVS. This can be converted -automatically to a `ChangeLog' file using `rcs2log'; in Emacs, the -command `C-x v a' (`vc-update-change-log') does the job. +version control system such as RCS or CVS. This can be converted +automatically to a 'ChangeLog' file using 'rcs2log'; in Emacs, the +command 'C-x v a' ('vc-update-change-log') does the job. There's no need to describe the full purpose of the changes or how they work together. However, sometimes it is useful to write one line to describe the overall purpose of a change or a batch of changes. If you think that a change calls for explanation, you're probably right. -Please do explain it--but please put the full explanation in comments -in the code, where people will see it whenever they see the code. For +Please do explain it--but please put the full explanation in comments in +the code, where people will see it whenever they see the code. For example, "New function" is enough for the change log when you add a function, because there should be a comment before the function definition to explain what it does. In the past, we recommended not mentioning changes in non-software -files (manuals, help files, etc.) in change logs. However, we've been +files (manuals, help files, etc.) in change logs. However, we've been advised that it is a good idea to include them, for the sake of copyright records. - The easiest way to add an entry to `ChangeLog' is with the Emacs -command `M-x add-change-log-entry'. An entry should have an asterisk, + The easiest way to add an entry to 'ChangeLog' is with the Emacs +command 'M-x add-change-log-entry'. An entry should have an asterisk, the name of the changed file, and then in parentheses the name of the changed functions, variables or whatever, followed by a colon. Then describe the changes you made to that function or variable. @@ -3378,8 +3369,8 @@ File: standards.info, Node: Style of Change Logs, Next: Simple Changes, Prev: Here are some simple examples of change log entries, starting with the header line that says who made the change and when it was installed, -followed by descriptions of specific changes. (These examples are -drawn from Emacs and GCC.) +followed by descriptions of specific changes. (These examples are drawn +from Emacs and GCC.) 1998-08-17 Richard Stallman <rms@gnu.org> @@ -3403,9 +3394,9 @@ the change log entries that pertain to it; if you abbreviate the name, they won't find it when they search. For example, some people are tempted to abbreviate groups of function -names by writing `* register.el ({insert,jump-to}-register)'; this is -not a good idea, since searching for `jump-to-register' or -`insert-register' would not find that entry. +names by writing '* register.el ({insert,jump-to}-register)'; this is +not a good idea, since searching for 'jump-to-register' or +'insert-register' would not find that entry. Separate unrelated change log entries with blank lines. When two entries represent parts of the same change, so that they work together, @@ -3413,7 +3404,7 @@ then don't put blank lines between them. Then you can omit the file name and the asterisk when successive entries are in the same file. Break long lists of function names by closing continued lines with -`)', rather than `,', and opening the continuation with `(' as in this +')', rather than ',', and opening the continuation with '(' as in this example: * keyboard.c (menu_bar_items, tool_bar_items) @@ -3475,10 +3466,10 @@ File: standards.info, Node: Conditional Changes, Next: Indicating the Part Cha 6.8.4 Conditional Changes ------------------------- -C programs often contain compile-time `#if' conditionals. Many changes +C programs often contain compile-time '#if' conditionals. Many changes are conditional; sometimes you add a new definition which is entirely -contained in a conditional. It is very useful to indicate in the -change log the conditions for which the change applies. +contained in a conditional. It is very useful to indicate in the change +log the conditions for which the change applies. Our convention for indicating conditional changes is to use square brackets around the name of the condition. @@ -3489,14 +3480,14 @@ but does not have a function or entity name associated with it: * xterm.c [SOLARIS2]: Include string.h. Here is an entry describing a new definition which is entirely -conditional. This new definition for the macro `FRAME_WINDOW_P' is -used only when `HAVE_X_WINDOWS' is defined: +conditional. This new definition for the macro 'FRAME_WINDOW_P' is used +only when 'HAVE_X_WINDOWS' is defined: * frame.h [HAVE_X_WINDOWS] (FRAME_WINDOW_P): Macro defined. - Here is an entry for a change within the function `init_display', + Here is an entry for a change within the function 'init_display', whose definition as a whole is unconditional, but the changes themselves -are contained in a `#ifdef HAVE_LIBNCURSES' conditional: +are contained in a '#ifdef HAVE_LIBNCURSES' conditional: * dispnew.c (init_display) [HAVE_LIBNCURSES]: If X, call tgetent. @@ -3513,8 +3504,8 @@ File: standards.info, Node: Indicating the Part Changed, Prev: Conditional Cha Indicate the part of a function which changed by using angle brackets enclosing an indication of what the changed part does. Here is an entry -for a change in the part of the function `sh-while-getopts' that deals -with `sh' commands: +for a change in the part of the function 'sh-while-getopts' that deals +with 'sh' commands: * progmodes/sh-script.el (sh-while-getopts) <sh>: Handle case that user-specified option string is empty. @@ -3538,12 +3529,12 @@ be a small job. Then there is little reason not to include a man page, if you have one. For a large program that changes a great deal, updating a man page -may be a substantial burden. If a user offers to donate a man page, -you may find this gift costly to accept. It may be better to refuse -the man page unless the same person agrees to take full responsibility -for maintaining it--so that you can wash your hands of it entirely. If -this volunteer later ceases to do the job, then don't feel obliged to -pick it up yourself; it may be better to withdraw the man page from the +may be a substantial burden. If a user offers to donate a man page, you +may find this gift costly to accept. It may be better to refuse the man +page unless the same person agrees to take full responsibility for +maintaining it--so that you can wash your hands of it entirely. If this +volunteer later ceases to do the job, then don't feel obliged to pick it +up yourself; it may be better to withdraw the man page from the distribution until someone else agrees to update it. When a program changes only a little, you may feel that the @@ -3555,16 +3546,15 @@ documentation. Be sure that man pages include a copyright statement and free license. The simple all-permissive license is appropriate for simple -man pages (*note License Notices for Other Files: (maintain)License -Notices for Other Files.). +man pages (*note (maintain)License Notices for Other Files::). For long man pages, with enough explanation and documentation that they can be considered true manuals, use the GFDL (*note License for Manuals::). Finally, the GNU help2man program -(`http://www.gnu.org/software/help2man/') is one way to automate -generation of a man page, in this case from `--help' output. This is +(<http://www.gnu.org/software/help2man/>) is one way to automate +generation of a man page, in this case from '--help' output. This is sufficient in many cases. @@ -3592,7 +3582,7 @@ File: standards.info, Node: Managing Releases, Next: References, Prev: Docume ********************* Making a release is more than just bundling up your source files in a -tar file and putting it up for FTP. You should set up your software so +tar file and putting it up for FTP. You should set up your software so that it can be configured to run on a variety of systems. Your Makefile should conform to the GNU standards described below, and your directory layout should also conform to the standards discussed below. Doing so @@ -3611,150 +3601,146 @@ File: standards.info, Node: Configuration, Next: Makefile Conventions, Up: Ma 7.1 How Configuration Should Work ================================= -Each GNU distribution should come with a shell script named -`configure'. This script is given arguments which describe the kind of -machine and system you want to compile the program for. The -`configure' script must record the configuration options so that they -affect compilation. +Each GNU distribution should come with a shell script named 'configure'. +This script is given arguments which describe the kind of machine and +system you want to compile the program for. The 'configure' script must +record the configuration options so that they affect compilation. The description here is the specification of the interface for the -`configure' script in GNU packages. Many packages implement it using -GNU Autoconf (*note Introduction: (autoconf)Top.) and/or GNU Automake +'configure' script in GNU packages. Many packages implement it using +GNU Autoconf (*note Introduction: (autoconf)Top.) and/or GNU Automake (*note Introduction: (automake)Top.), but you do not have to use these tools. You can implement it any way you like; for instance, by making -`configure' be a wrapper around a completely different configuration +'configure' be a wrapper around a completely different configuration system. - Another way for the `configure' script to operate is to make a link -from a standard name such as `config.h' to the proper configuration -file for the chosen system. If you use this technique, the -distribution should _not_ contain a file named `config.h'. This is so -that people won't be able to build the program without configuring it -first. + Another way for the 'configure' script to operate is to make a link +from a standard name such as 'config.h' to the proper configuration file +for the chosen system. If you use this technique, the distribution +should _not_ contain a file named 'config.h'. This is so that people +won't be able to build the program without configuring it first. - Another thing that `configure' can do is to edit the Makefile. If + Another thing that 'configure' can do is to edit the Makefile. If you do this, the distribution should _not_ contain a file named -`Makefile'. Instead, it should include a file `Makefile.in' which +'Makefile'. Instead, it should include a file 'Makefile.in' which contains the input used for editing. Once again, this is so that people won't be able to build the program without configuring it first. - If `configure' does write the `Makefile', then `Makefile' should -have a target named `Makefile' which causes `configure' to be rerun, -setting up the same configuration that was set up last time. The files -that `configure' reads should be listed as dependencies of `Makefile'. + If 'configure' does write the 'Makefile', then 'Makefile' should have +a target named 'Makefile' which causes 'configure' to be rerun, setting +up the same configuration that was set up last time. The files that +'configure' reads should be listed as dependencies of 'Makefile'. - All the files which are output from the `configure' script should + All the files which are output from the 'configure' script should have comments at the beginning explaining that they were generated -automatically using `configure'. This is so that users won't think of +automatically using 'configure'. This is so that users won't think of trying to edit them by hand. - The `configure' script should write a file named `config.status' + The 'configure' script should write a file named 'config.status' which describes which configuration options were specified when the program was last configured. This file should be a shell script which, if run, will recreate the same configuration. - The `configure' script should accept an option of the form -`--srcdir=DIRNAME' to specify the directory where sources are found (if + The 'configure' script should accept an option of the form +'--srcdir=DIRNAME' to specify the directory where sources are found (if it is not the current directory). This makes it possible to build the program in a separate directory, so that the actual source directory is not modified. - If the user does not specify `--srcdir', then `configure' should -check both `.' and `..' to see if it can find the sources. If it finds + If the user does not specify '--srcdir', then 'configure' should +check both '.' and '..' to see if it can find the sources. If it finds the sources in one of these places, it should use them from there. Otherwise, it should report that it cannot find the sources, and should exit with nonzero status. - Usually the easy way to support `--srcdir' is by editing a -definition of `VPATH' into the Makefile. Some rules may need to refer -explicitly to the specified source directory. To make this possible, -`configure' can add to the Makefile a variable named `srcdir' whose -value is precisely the specified directory. + Usually the easy way to support '--srcdir' is by editing a definition +of 'VPATH' into the Makefile. Some rules may need to refer explicitly +to the specified source directory. To make this possible, 'configure' +can add to the Makefile a variable named 'srcdir' whose value is +precisely the specified directory. - In addition, the `configure' script should take options -corresponding to most of the standard directory variables (*note -Directory Variables::). Here is the list: + In addition, the 'configure' script should take options corresponding +to most of the standard directory variables (*note Directory +Variables::). Here is the list: --prefix --exec-prefix --bindir --sbindir --libexecdir --sysconfdir --sharedstatedir --localstatedir --libdir --includedir --oldincludedir --datarootdir --datadir --infodir --localedir --mandir --docdir --htmldir --dvidir --pdfdir --psdir - The `configure' script should also take an argument which specifies + The 'configure' script should also take an argument which specifies the type of system to build the program for. This argument should look like this: CPU-COMPANY-SYSTEM For example, an Athlon-based GNU/Linux system might be -`i686-pc-linux-gnu'. +'i686-pc-linux-gnu'. - The `configure' script needs to be able to decode all plausible -alternatives for how to describe a machine. Thus, -`athlon-pc-gnu/linux' would be a valid alias. There is a shell script -called `config.sub' + The 'configure' script needs to be able to decode all plausible +alternatives for how to describe a machine. Thus, 'athlon-pc-gnu/linux' +would be a valid alias. There is a shell script called 'config.sub' (http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD) that you can use as a subroutine to validate system types and canonicalize aliases. - The `configure' script should also take the option -`--build=BUILDTYPE', which should be equivalent to a plain BUILDTYPE -argument. For example, `configure --build=i686-pc-linux-gnu' is -equivalent to `configure i686-pc-linux-gnu'. When the build type is -not specified by an option or argument, the `configure' script should -normally guess it using the shell script `config.guess' + The 'configure' script should also take the option +'--build=BUILDTYPE', which should be equivalent to a plain BUILDTYPE +argument. For example, 'configure --build=i686-pc-linux-gnu' is +equivalent to 'configure i686-pc-linux-gnu'. When the build type is not +specified by an option or argument, the 'configure' script should +normally guess it using the shell script 'config.guess' (http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD). - Other options are permitted to specify in more detail the software -or hardware present on the machine, to include or exclude optional parts -of the package, or to adjust the name of some tools or arguments to -them: + Other options are permitted to specify in more detail the software or +hardware present on the machine, to include or exclude optional parts of +the package, or to adjust the name of some tools or arguments to them: -`--enable-FEATURE[=PARAMETER]' +'--enable-FEATURE[=PARAMETER]' Configure the package to build and install an optional user-level facility called FEATURE. This allows users to choose which - optional features to include. Giving an optional PARAMETER of - `no' should omit FEATURE, if it is built by default. + optional features to include. Giving an optional PARAMETER of 'no' + should omit FEATURE, if it is built by default. - No `--enable' option should *ever* cause one feature to replace - another. No `--enable' option should ever substitute one useful + No '--enable' option should *ever* cause one feature to replace + another. No '--enable' option should ever substitute one useful behavior for another useful behavior. The only proper use for - `--enable' is for questions of whether to build part of the program + '--enable' is for questions of whether to build part of the program or exclude it. -`--with-PACKAGE' - The package PACKAGE will be installed, so configure this package - to work with PACKAGE. +'--with-PACKAGE' + The package PACKAGE will be installed, so configure this package to + work with PACKAGE. - Possible values of PACKAGE include `gnu-as' (or `gas'), `gnu-ld', - `gnu-libc', `gdb', `x', and `x-toolkit'. + Possible values of PACKAGE include 'gnu-as' (or 'gas'), 'gnu-ld', + 'gnu-libc', 'gdb', 'x', and 'x-toolkit'. - Do not use a `--with' option to specify the file name to use to - find certain files. That is outside the scope of what `--with' + Do not use a '--with' option to specify the file name to use to + find certain files. That is outside the scope of what '--with' options are for. -`VARIABLE=VALUE' +'VARIABLE=VALUE' Set the value of the variable VARIABLE to VALUE. This is used to override the default values of commands or arguments in the build - process. For example, the user could issue `configure CFLAGS=-g + process. For example, the user could issue 'configure CFLAGS=-g CXXFLAGS=-g' to build with debugging information and without the default optimization. - Specifying variables as arguments to `configure', like this: + Specifying variables as arguments to 'configure', like this: ./configure CC=gcc is preferable to setting them in environment variables: CC=gcc ./configure as it helps to recreate the same configuration later with - `config.status'. However, both methods should be supported. + 'config.status'. However, both methods should be supported. - All `configure' scripts should accept all of the "detail" options -and the variable settings, whether or not they make any difference to -the particular package at hand. In particular, they should accept any -option that starts with `--with-' or `--enable-'. This is so users -will be able to configure an entire GNU source tree at once with a -single set of options. + All 'configure' scripts should accept all of the "detail" options and +the variable settings, whether or not they make any difference to the +particular package at hand. In particular, they should accept any +option that starts with '--with-' or '--enable-'. This is so users will +be able to configure an entire GNU source tree at once with a single set +of options. - You will note that the categories `--with-' and `--enable-' are + You will note that the categories '--with-' and '--enable-' are narrow: they *do not* provide a place for any sort of option you might think of. That is deliberate. We want to limit the possible configuration options in GNU software. We do not want GNU programs to @@ -3764,29 +3750,29 @@ have idiosyncratic configuration options. cross-compilation. In such a case, the host and target machines for the program may be different. - The `configure' script should normally treat the specified type of + The 'configure' script should normally treat the specified type of system as both the host and the target, thus producing a program which works for the same type of machine that it runs on. To compile a program to run on a host type that differs from the -build type, use the configure option `--host=HOSTTYPE', where HOSTTYPE +build type, use the configure option '--host=HOSTTYPE', where HOSTTYPE uses the same syntax as BUILDTYPE. The host type normally defaults to the build type. To configure a cross-compiler, cross-assembler, or what have you, you should specify a target different from the host, using the configure -option `--target=TARGETTYPE'. The syntax for TARGETTYPE is the same as +option '--target=TARGETTYPE'. The syntax for TARGETTYPE is the same as for the host type. So the command would look like this: ./configure --host=HOSTTYPE --target=TARGETTYPE The target type normally defaults to the host type. Programs for -which cross-operation is not meaningful need not accept the `--target' +which cross-operation is not meaningful need not accept the '--target' option, because configuring an entire operating system for cross-operation is not a meaningful operation. Some programs have ways of configuring themselves automatically. If -your program is set up to do this, your `configure' script can simply +your program is set up to do this, your 'configure' script can simply ignore most of its arguments. @@ -3807,7 +3793,7 @@ these conventions. * DESTDIR:: Supporting staged installs. * Directory Variables:: Variables for installation directories. * Standard Targets:: Standard targets for users. -* Install Command Categories:: Three categories of commands in the `install' +* Install Command Categories:: Three categories of commands in the 'install' rule: normal, pre-install and post-install. @@ -3820,14 +3806,14 @@ Every Makefile should contain this line: SHELL = /bin/sh -to avoid trouble on systems where the `SHELL' variable might be +to avoid trouble on systems where the 'SHELL' variable might be inherited from the environment. (This is never a problem with GNU -`make'.) +'make'.) - Different `make' programs have incompatible suffix lists and -implicit rules, and this sometimes creates confusion or misbehavior. So -it is a good idea to set the suffix list explicitly using only the -suffixes you need in the particular Makefile, like this: + Different 'make' programs have incompatible suffix lists and implicit +rules, and this sometimes creates confusion or misbehavior. So it is a +good idea to set the suffix list explicitly using only the suffixes you +need in the particular Makefile, like this: .SUFFIXES: .SUFFIXES: .c .o @@ -3835,29 +3821,28 @@ suffixes you need in the particular Makefile, like this: The first line clears out the suffix list, the second introduces all suffixes which may be subject to implicit rules in this Makefile. - Don't assume that `.' is in the path for command execution. When -you need to run programs that are a part of your package during the -make, please make sure that it uses `./' if the program is built as -part of the make or `$(srcdir)/' if the file is an unchanging part of -the source code. Without one of these prefixes, the current search -path is used. + Don't assume that '.' is in the path for command execution. When you +need to run programs that are a part of your package during the make, +please make sure that it uses './' if the program is built as part of +the make or '$(srcdir)/' if the file is an unchanging part of the source +code. Without one of these prefixes, the current search path is used. - The distinction between `./' (the "build directory") and -`$(srcdir)/' (the "source directory") is important because users can -build in a separate directory using the `--srcdir' option to -`configure'. A rule of the form: + The distinction between './' (the "build directory") and '$(srcdir)/' +(the "source directory") is important because users can build in a +separate directory using the '--srcdir' option to 'configure'. A rule +of the form: foo.1 : foo.man sedscript sed -e sedscript foo.man > foo.1 will fail when the build directory is not the source directory, because -`foo.man' and `sedscript' are in the source directory. +'foo.man' and 'sedscript' are in the source directory. - When using GNU `make', relying on `VPATH' to find the source file -will work in the case where there is a single dependency file, since -the `make' automatic variable `$<' will represent the source file -wherever it is. (Many versions of `make' set `$<' only in implicit -rules.) A Makefile target like + When using GNU 'make', relying on 'VPATH' to find the source file +will work in the case where there is a single dependency file, since the +'make' automatic variable '$<' will represent the source file wherever +it is. (Many versions of 'make' set '$<' only in implicit rules.) A +Makefile target like foo.o : bar.c $(CC) -I. -I$(srcdir) $(CFLAGS) -c bar.c -o foo.o @@ -3867,9 +3852,9 @@ should instead be written as foo.o : bar.c $(CC) -I. -I$(srcdir) $(CFLAGS) -c $< -o $@ -in order to allow `VPATH' to work correctly. When the target has -multiple dependencies, using an explicit `$(srcdir)' is the easiest way -to make the rule work well. For example, the target above for `foo.1' +in order to allow 'VPATH' to work correctly. When the target has +multiple dependencies, using an explicit '$(srcdir)' is the easiest way +to make the rule work well. For example, the target above for 'foo.1' is best written as: foo.1 : foo.man sedscript @@ -3888,7 +3873,7 @@ program in ordinary circumstances should not modify the source directory in any way. Try to make the build and installation targets, at least (and all -their subtargets) work correctly with a parallel `make'. +their subtargets) work correctly with a parallel 'make'. File: standards.info, Node: Utilities in Makefiles, Next: Command Variables, Prev: Makefile Basics, Up: Makefile Conventions @@ -3896,43 +3881,43 @@ File: standards.info, Node: Utilities in Makefiles, Next: Command Variables, 7.2.2 Utilities in Makefiles ---------------------------- -Write the Makefile commands (and any shell scripts, such as -`configure') to run in `sh', not in `csh'. Don't use any special -features of `ksh' or `bash'. +Write the Makefile commands (and any shell scripts, such as 'configure') +to run in 'sh', not in 'csh'. Don't use any special features of 'ksh' +or 'bash'. - The `configure' script and the Makefile rules for building and + The 'configure' script and the Makefile rules for building and installation should not use any utilities directly except these: cat cmp cp diff echo egrep expr false grep install-info ln ls mkdir mv pwd rm rmdir sed sleep sort tar test touch true - The compression program `gzip' can be used in the `dist' rule. + The compression program 'gzip' can be used in the 'dist' rule. Stick to the generally supported options for these programs. For -example, don't use `mkdir -p', convenient as it may be, because most +example, don't use 'mkdir -p', convenient as it may be, because most systems don't support it. It is a good idea to avoid creating symbolic links in makefiles, since a few systems don't support them. The Makefile rules for building and installation can also use -compilers and related programs, but should do so via `make' variables -so that the user can substitute alternatives. Here are some of the +compilers and related programs, but should do so via 'make' variables so +that the user can substitute alternatives. Here are some of the programs we mean: ar bison cc flex install ld ldconfig lex make makeinfo ranlib texi2dvi yacc - Use the following `make' variables to run those programs: + Use the following 'make' variables to run those programs: $(AR) $(BISON) $(CC) $(FLEX) $(INSTALL) $(LD) $(LDCONFIG) $(LEX) $(MAKE) $(MAKEINFO) $(RANLIB) $(TEXI2DVI) $(YACC) - When you use `ranlib' or `ldconfig', you should make sure nothing -bad happens if the system does not have the program in question. -Arrange to ignore an error from that command, and print a message before -the command to tell the user that failure of this command does not mean -a problem. (The Autoconf `AC_PROG_RANLIB' macro can help with this.) + When you use 'ranlib' or 'ldconfig', you should make sure nothing bad +happens if the system does not have the program in question. Arrange to +ignore an error from that command, and print a message before the +command to tell the user that failure of this command does not mean a +problem. (The Autoconf 'AC_PROG_RANLIB' macro can help with this.) If you use symbolic links, you should implement a fallback for systems that don't have symbolic links. @@ -3955,64 +3940,63 @@ Makefiles should provide variables for overriding certain commands, options, and so on. In particular, you should run most utility programs via variables. -Thus, if you use Bison, have a variable named `BISON' whose default -value is set with `BISON = bison', and refer to it with `$(BISON)' +Thus, if you use Bison, have a variable named 'BISON' whose default +value is set with 'BISON = bison', and refer to it with '$(BISON)' whenever you need to use Bison. - File management utilities such as `ln', `rm', `mv', and so on, need -not be referred to through variables in this way, since users don't -need to replace them with other programs. + File management utilities such as 'ln', 'rm', 'mv', and so on, need +not be referred to through variables in this way, since users don't need +to replace them with other programs. Each program-name variable should come with an options variable that -is used to supply options to the program. Append `FLAGS' to the +is used to supply options to the program. Append 'FLAGS' to the program-name variable name to get the options variable name--for -example, `BISONFLAGS'. (The names `CFLAGS' for the C compiler, -`YFLAGS' for yacc, and `LFLAGS' for lex, are exceptions to this rule, -but we keep them because they are standard.) Use `CPPFLAGS' in any -compilation command that runs the preprocessor, and use `LDFLAGS' in -any compilation command that does linking as well as in any direct use -of `ld'. +example, 'BISONFLAGS'. (The names 'CFLAGS' for the C compiler, 'YFLAGS' +for yacc, and 'LFLAGS' for lex, are exceptions to this rule, but we keep +them because they are standard.) Use 'CPPFLAGS' in any compilation +command that runs the preprocessor, and use 'LDFLAGS' in any compilation +command that does linking as well as in any direct use of 'ld'. If there are C compiler options that _must_ be used for proper -compilation of certain files, do not include them in `CFLAGS'. Users -expect to be able to specify `CFLAGS' freely themselves. Instead, -arrange to pass the necessary options to the C compiler independently -of `CFLAGS', by writing them explicitly in the compilation commands or -by defining an implicit rule, like this: +compilation of certain files, do not include them in 'CFLAGS'. Users +expect to be able to specify 'CFLAGS' freely themselves. Instead, +arrange to pass the necessary options to the C compiler independently of +'CFLAGS', by writing them explicitly in the compilation commands or by +defining an implicit rule, like this: CFLAGS = -g ALL_CFLAGS = -I. $(CFLAGS) .c.o: $(CC) -c $(CPPFLAGS) $(ALL_CFLAGS) $< - Do include the `-g' option in `CFLAGS', because that is not + Do include the '-g' option in 'CFLAGS', because that is not _required_ for proper compilation. You can consider it a default that is only recommended. If the package is set up so that it is compiled -with GCC by default, then you might as well include `-O' in the default -value of `CFLAGS' as well. +with GCC by default, then you might as well include '-O' in the default +value of 'CFLAGS' as well. - Put `CFLAGS' last in the compilation command, after other variables -containing compiler options, so the user can use `CFLAGS' to override + Put 'CFLAGS' last in the compilation command, after other variables +containing compiler options, so the user can use 'CFLAGS' to override the others. - `CFLAGS' should be used in every invocation of the C compiler, both + 'CFLAGS' should be used in every invocation of the C compiler, both those which do compilation and those which do linking. - Every Makefile should define the variable `INSTALL', which is the + Every Makefile should define the variable 'INSTALL', which is the basic command for installing a file into the system. - Every Makefile should also define the variables `INSTALL_PROGRAM' -and `INSTALL_DATA'. (The default for `INSTALL_PROGRAM' should be -`$(INSTALL)'; the default for `INSTALL_DATA' should be `${INSTALL} -m + Every Makefile should also define the variables 'INSTALL_PROGRAM' and +'INSTALL_DATA'. (The default for 'INSTALL_PROGRAM' should be +'$(INSTALL)'; the default for 'INSTALL_DATA' should be '${INSTALL} -m 644'.) Then it should use those variables as the commands for actual -installation, for executables and non-executables respectively. -Minimal use of these variables is as follows: +installation, for executables and non-executables respectively. Minimal +use of these variables is as follows: $(INSTALL_PROGRAM) foo $(bindir)/foo $(INSTALL_DATA) libfoo.a $(libdir)/libfoo.a - However, it is preferable to support a `DESTDIR' prefix on the -target files, as explained in the next section. + However, it is preferable to support a 'DESTDIR' prefix on the target +files, as explained in the next section. Always use a file name, not a directory name, as the second argument of the installation commands. Use a separate command for each file to be @@ -4021,51 +4005,49 @@ installed. File: standards.info, Node: DESTDIR, Next: Directory Variables, Prev: Command Variables, Up: Makefile Conventions -7.2.4 `DESTDIR': support for staged installs +7.2.4 'DESTDIR': support for staged installs -------------------------------------------- -`DESTDIR' is a variable prepended to each installed target file, like +'DESTDIR' is a variable prepended to each installed target file, like this: $(INSTALL_PROGRAM) foo $(DESTDIR)$(bindir)/foo $(INSTALL_DATA) libfoo.a $(DESTDIR)$(libdir)/libfoo.a - The `DESTDIR' variable is specified by the user on the `make' -command line. For example: + The 'DESTDIR' variable is specified by the user on the 'make' command +line. For example: make DESTDIR=/tmp/stage install -`DESTDIR' should be supported only in the `install*' and `uninstall*' +'DESTDIR' should be supported only in the 'install*' and 'uninstall*' targets, as those are the only targets where it is useful. - If your installation step would normally install -`/usr/local/bin/foo' and `/usr/local/lib/libfoo.a', then an -installation invoked as in the example above would install -`/tmp/stage/usr/local/bin/foo' and `/tmp/stage/usr/local/lib/libfoo.a' -instead. + If your installation step would normally install '/usr/local/bin/foo' +and '/usr/local/lib/libfoo.a', then an installation invoked as in the +example above would install '/tmp/stage/usr/local/bin/foo' and +'/tmp/stage/usr/local/lib/libfoo.a' instead. - Prepending the variable `DESTDIR' to each target in this way -provides for "staged installs", where the installed files are not -placed directly into their expected location but are instead copied -into a temporary location (`DESTDIR'). However, installed files -maintain their relative directory structure and any embedded file names -will not be modified. + Prepending the variable 'DESTDIR' to each target in this way provides +for "staged installs", where the installed files are not placed directly +into their expected location but are instead copied into a temporary +location ('DESTDIR'). However, installed files maintain their relative +directory structure and any embedded file names will not be modified. - You should not set the value of `DESTDIR' in your `Makefile' at all; + You should not set the value of 'DESTDIR' in your 'Makefile' at all; then the files are installed into their expected locations by default. -Also, specifying `DESTDIR' should not change the operation of the +Also, specifying 'DESTDIR' should not change the operation of the software in any way, so its value should not be included in any file contents. - `DESTDIR' support is commonly used in package creation. It is also + 'DESTDIR' support is commonly used in package creation. It is also helpful to users who want to understand what a given package will -install where, and to allow users who don't normally have permissions -to install into protected areas to build and install before gaining -those permissions. Finally, it can be useful with tools such as -`stow', where code is installed in one place but made to appear to be -installed somewhere else using symbolic links or special mount -operations. So, we strongly recommend GNU packages support `DESTDIR', -though it is not an absolute requirement. +install where, and to allow users who don't normally have permissions to +install into protected areas to build and install before gaining those +permissions. Finally, it can be useful with tools such as 'stow', where +code is installed in one place but made to appear to be installed +somewhere else using symbolic links or special mount operations. So, we +strongly recommend GNU packages support 'DESTDIR', though it is not an +absolute requirement. File: standards.info, Node: Directory Variables, Next: Standard Targets, Prev: DESTDIR, Up: Makefile Conventions @@ -4079,8 +4061,8 @@ variables and the values they should have in GNU packages are described below. They are based on a standard file system layout; variants of it are used in GNU/Linux and other modern operating systems. - Installers are expected to override these values when calling `make' -(e.g., `make prefix=/usr install' or `configure' (e.g., `configure + Installers are expected to override these values when calling 'make' +(e.g., 'make prefix=/usr install' or 'configure' (e.g., 'configure --prefix=/usr'). GNU packages should not try to guess which value should be appropriate for these variables on the system they are being installed onto: use the default settings specified here so that all GNU @@ -4092,58 +4074,58 @@ other installation directories should be subdirectories of one of these two, and nothing should be directly installed into these two directories. -`prefix' +'prefix' A prefix used in constructing the default values of the variables - listed below. The default value of `prefix' should be - `/usr/local'. When building the complete GNU system, the prefix - will be empty and `/usr' will be a symbolic link to `/'. (If you - are using Autoconf, write it as `@prefix@'.) + listed below. The default value of 'prefix' should be + '/usr/local'. When building the complete GNU system, the prefix + will be empty and '/usr' will be a symbolic link to '/'. (If you + are using Autoconf, write it as '@prefix@'.) - Running `make install' with a different value of `prefix' from the + Running 'make install' with a different value of 'prefix' from the one used to build the program should _not_ recompile the program. -`exec_prefix' +'exec_prefix' A prefix used in constructing the default values of some of the - variables listed below. The default value of `exec_prefix' should - be `$(prefix)'. (If you are using Autoconf, write it as - `@exec_prefix@'.) + variables listed below. The default value of 'exec_prefix' should + be '$(prefix)'. (If you are using Autoconf, write it as + '@exec_prefix@'.) - Generally, `$(exec_prefix)' is used for directories that contain + Generally, '$(exec_prefix)' is used for directories that contain machine-specific files (such as executables and subroutine - libraries), while `$(prefix)' is used directly for other + libraries), while '$(prefix)' is used directly for other directories. - Running `make install' with a different value of `exec_prefix' - from the one used to build the program should _not_ recompile the + Running 'make install' with a different value of 'exec_prefix' from + the one used to build the program should _not_ recompile the program. Executable programs are installed in one of the following directories. -`bindir' +'bindir' The directory for installing executable programs that users can - run. This should normally be `/usr/local/bin', but write it as - `$(exec_prefix)/bin'. (If you are using Autoconf, write it as - `@bindir@'.) + run. This should normally be '/usr/local/bin', but write it as + '$(exec_prefix)/bin'. (If you are using Autoconf, write it as + '@bindir@'.) -`sbindir' +'sbindir' The directory for installing executable programs that can be run from the shell, but are only generally useful to system - administrators. This should normally be `/usr/local/sbin', but - write it as `$(exec_prefix)/sbin'. (If you are using Autoconf, - write it as `@sbindir@'.) + administrators. This should normally be '/usr/local/sbin', but + write it as '$(exec_prefix)/sbin'. (If you are using Autoconf, + write it as '@sbindir@'.) -`libexecdir' +'libexecdir' The directory for installing executable programs to be run by other programs rather than by users. This directory should normally be - `/usr/local/libexec', but write it as `$(exec_prefix)/libexec'. - (If you are using Autoconf, write it as `@libexecdir@'.) + '/usr/local/libexec', but write it as '$(exec_prefix)/libexec'. + (If you are using Autoconf, write it as '@libexecdir@'.) - The definition of `libexecdir' is the same for all packages, so - you should install your data in a subdirectory thereof. Most - packages install their data under `$(libexecdir)/PACKAGE-NAME/', - possibly within additional subdirectories thereof, such as - `$(libexecdir)/PACKAGE-NAME/MACHINE/VERSION'. + The definition of 'libexecdir' is the same for all packages, so you + should install your data in a subdirectory thereof. Most packages + install their data under '$(libexecdir)/PACKAGE-NAME/', possibly + within additional subdirectories thereof, such as + '$(libexecdir)/PACKAGE-NAME/MACHINE/VERSION'. Data files used by the program during its execution are divided into categories in two ways. @@ -4161,199 +4143,195 @@ discourage the use of architecture-dependent files, aside from object files and libraries. It is much cleaner to make other data files architecture-independent, and it is generally not hard. - Here are the variables Makefiles should use to specify directories -to put these various kinds of files in: + Here are the variables Makefiles should use to specify directories to +put these various kinds of files in: -`datarootdir' +'datarootdir' The root of the directory tree for read-only architecture-independent data files. This should normally be - `/usr/local/share', but write it as `$(prefix)/share'. (If you - are using Autoconf, write it as `@datarootdir@'.) `datadir''s - default value is based on this variable; so are `infodir', - `mandir', and others. + '/usr/local/share', but write it as '$(prefix)/share'. (If you are + using Autoconf, write it as '@datarootdir@'.) 'datadir''s default + value is based on this variable; so are 'infodir', 'mandir', and + others. -`datadir' +'datadir' The directory for installing idiosyncratic read-only architecture-independent data files for this program. This is - usually the same place as `datarootdir', but we use the two + usually the same place as 'datarootdir', but we use the two separate variables so that you can move these program-specific files without altering the location for Info files, man pages, etc. - This should normally be `/usr/local/share', but write it as - `$(datarootdir)'. (If you are using Autoconf, write it as - `@datadir@'.) + This should normally be '/usr/local/share', but write it as + '$(datarootdir)'. (If you are using Autoconf, write it as + '@datadir@'.) - The definition of `datadir' is the same for all packages, so you + The definition of 'datadir' is the same for all packages, so you should install your data in a subdirectory thereof. Most packages - install their data under `$(datadir)/PACKAGE-NAME/'. + install their data under '$(datadir)/PACKAGE-NAME/'. -`sysconfdir' +'sysconfdir' The directory for installing read-only data files that pertain to a single machine-that is to say, files for configuring a host. - Mailer and network configuration files, `/etc/passwd', and so - forth belong here. All the files in this directory should be - ordinary ASCII text files. This directory should normally be - `/usr/local/etc', but write it as `$(prefix)/etc'. (If you are - using Autoconf, write it as `@sysconfdir@'.) + Mailer and network configuration files, '/etc/passwd', and so forth + belong here. All the files in this directory should be ordinary + ASCII text files. This directory should normally be + '/usr/local/etc', but write it as '$(prefix)/etc'. (If you are + using Autoconf, write it as '@sysconfdir@'.) Do not install executables here in this directory (they probably - belong in `$(libexecdir)' or `$(sbindir)'). Also do not install + belong in '$(libexecdir)' or '$(sbindir)'). Also do not install files that are modified in the normal course of their use (programs whose purpose is to change the configuration of the system - excluded). Those probably belong in `$(localstatedir)'. + excluded). Those probably belong in '$(localstatedir)'. -`sharedstatedir' +'sharedstatedir' The directory for installing architecture-independent data files which the programs modify while they run. This should normally be - `/usr/local/com', but write it as `$(prefix)/com'. (If you are - using Autoconf, write it as `@sharedstatedir@'.) + '/usr/local/com', but write it as '$(prefix)/com'. (If you are + using Autoconf, write it as '@sharedstatedir@'.) -`localstatedir' +'localstatedir' The directory for installing data files which the programs modify while they run, and that pertain to one specific machine. Users should never need to modify files in this directory to configure the package's operation; put such configuration information in - separate files that go in `$(datadir)' or `$(sysconfdir)'. - `$(localstatedir)' should normally be `/usr/local/var', but write - it as `$(prefix)/var'. (If you are using Autoconf, write it as - `@localstatedir@'.) + separate files that go in '$(datadir)' or '$(sysconfdir)'. + '$(localstatedir)' should normally be '/usr/local/var', but write + it as '$(prefix)/var'. (If you are using Autoconf, write it as + '@localstatedir@'.) These variables specify the directory for installing certain specific -types of files, if your program has them. Every GNU package should -have Info files, so every program needs `infodir', but not all need -`libdir' or `lispdir'. +types of files, if your program has them. Every GNU package should have +Info files, so every program needs 'infodir', but not all need 'libdir' +or 'lispdir'. -`includedir' +'includedir' The directory for installing header files to be included by user - programs with the C `#include' preprocessor directive. This - should normally be `/usr/local/include', but write it as - `$(prefix)/include'. (If you are using Autoconf, write it as - `@includedir@'.) + programs with the C '#include' preprocessor directive. This should + normally be '/usr/local/include', but write it as + '$(prefix)/include'. (If you are using Autoconf, write it as + '@includedir@'.) Most compilers other than GCC do not look for header files in - directory `/usr/local/include'. So installing the header files - this way is only useful with GCC. Sometimes this is not a problem + directory '/usr/local/include'. So installing the header files + this way is only useful with GCC. Sometimes this is not a problem because some libraries are only really intended to work with GCC. - But some libraries are intended to work with other compilers. - They should install their header files in two places, one - specified by `includedir' and one specified by `oldincludedir'. + But some libraries are intended to work with other compilers. They + should install their header files in two places, one specified by + 'includedir' and one specified by 'oldincludedir'. -`oldincludedir' - The directory for installing `#include' header files for use with - compilers other than GCC. This should normally be `/usr/include'. - (If you are using Autoconf, you can write it as `@oldincludedir@'.) +'oldincludedir' + The directory for installing '#include' header files for use with + compilers other than GCC. This should normally be '/usr/include'. + (If you are using Autoconf, you can write it as '@oldincludedir@'.) The Makefile commands should check whether the value of - `oldincludedir' is empty. If it is, they should not try to use - it; they should cancel the second installation of the header files. + 'oldincludedir' is empty. If it is, they should not try to use it; + they should cancel the second installation of the header files. A package should not replace an existing header in this directory unless the header came from the same package. Thus, if your Foo - package provides a header file `foo.h', then it should install the - header file in the `oldincludedir' directory if either (1) there - is no `foo.h' there or (2) the `foo.h' that exists came from the - Foo package. + package provides a header file 'foo.h', then it should install the + header file in the 'oldincludedir' directory if either (1) there is + no 'foo.h' there or (2) the 'foo.h' that exists came from the Foo + package. - To tell whether `foo.h' came from the Foo package, put a magic - string in the file--part of a comment--and `grep' for that string. + To tell whether 'foo.h' came from the Foo package, put a magic + string in the file--part of a comment--and 'grep' for that string. -`docdir' +'docdir' The directory for installing documentation files (other than Info) for this package. By default, it should be - `/usr/local/share/doc/YOURPKG', but it should be written as - `$(datarootdir)/doc/YOURPKG'. (If you are using Autoconf, write - it as `@docdir@'.) The YOURPKG subdirectory, which may include a + '/usr/local/share/doc/YOURPKG', but it should be written as + '$(datarootdir)/doc/YOURPKG'. (If you are using Autoconf, write it + as '@docdir@'.) The YOURPKG subdirectory, which may include a version number, prevents collisions among files with common names, - such as `README'. + such as 'README'. -`infodir' +'infodir' The directory for installing the Info files for this package. By - default, it should be `/usr/local/share/info', but it should be - written as `$(datarootdir)/info'. (If you are using Autoconf, - write it as `@infodir@'.) `infodir' is separate from `docdir' for + default, it should be '/usr/local/share/info', but it should be + written as '$(datarootdir)/info'. (If you are using Autoconf, + write it as '@infodir@'.) 'infodir' is separate from 'docdir' for compatibility with existing practice. -`htmldir' -`dvidir' -`pdfdir' -`psdir' +'htmldir' +'dvidir' +'pdfdir' +'psdir' Directories for installing documentation files in the particular - format. They should all be set to `$(docdir)' by default. (If - you are using Autoconf, write them as `@htmldir@', `@dvidir@', - etc.) Packages which supply several translations of their - documentation should install them in `$(htmldir)/'LL, - `$(pdfdir)/'LL, etc. where LL is a locale abbreviation such as - `en' or `pt_BR'. - -`libdir' + format. They should all be set to '$(docdir)' by default. (If you + are using Autoconf, write them as '@htmldir@', '@dvidir@', etc.) + Packages which supply several translations of their documentation + should install them in '$(htmldir)/'LL, '$(pdfdir)/'LL, etc. where + LL is a locale abbreviation such as 'en' or 'pt_BR'. + +'libdir' The directory for object files and libraries of object code. Do not install executables here, they probably ought to go in - `$(libexecdir)' instead. The value of `libdir' should normally be - `/usr/local/lib', but write it as `$(exec_prefix)/lib'. (If you - are using Autoconf, write it as `@libdir@'.) + '$(libexecdir)' instead. The value of 'libdir' should normally be + '/usr/local/lib', but write it as '$(exec_prefix)/lib'. (If you + are using Autoconf, write it as '@libdir@'.) -`lispdir' +'lispdir' The directory for installing any Emacs Lisp files in this package. - By default, it should be `/usr/local/share/emacs/site-lisp', but it - should be written as `$(datarootdir)/emacs/site-lisp'. + By default, it should be '/usr/local/share/emacs/site-lisp', but it + should be written as '$(datarootdir)/emacs/site-lisp'. - If you are using Autoconf, write the default as `@lispdir@'. In - order to make `@lispdir@' work, you need the following lines in - your `configure.in' file: + If you are using Autoconf, write the default as '@lispdir@'. In + order to make '@lispdir@' work, you need the following lines in + your 'configure.in' file: lispdir='${datarootdir}/emacs/site-lisp' AC_SUBST(lispdir) -`localedir' +'localedir' The directory for installing locale-specific message catalogs for - this package. By default, it should be `/usr/local/share/locale', - but it should be written as `$(datarootdir)/locale'. (If you are - using Autoconf, write it as `@localedir@'.) This directory - usually has a subdirectory per locale. + this package. By default, it should be '/usr/local/share/locale', + but it should be written as '$(datarootdir)/locale'. (If you are + using Autoconf, write it as '@localedir@'.) This directory usually + has a subdirectory per locale. Unix-style man pages are installed in one of the following: -`mandir' +'mandir' The top-level directory for installing the man pages (if any) for - this package. It will normally be `/usr/local/share/man', but you - should write it as `$(datarootdir)/man'. (If you are using - Autoconf, write it as `@mandir@'.) + this package. It will normally be '/usr/local/share/man', but you + should write it as '$(datarootdir)/man'. (If you are using + Autoconf, write it as '@mandir@'.) -`man1dir' +'man1dir' The directory for installing section 1 man pages. Write it as - `$(mandir)/man1'. - -`man2dir' + '$(mandir)/man1'. +'man2dir' The directory for installing section 2 man pages. Write it as - `$(mandir)/man2' + '$(mandir)/man2' +'...' -`...' - *Don't make the primary documentation for any GNU software be a - man page. Write a manual in Texinfo instead. Man pages are just - for the sake of people running GNU software on Unix, which is a + *Don't make the primary documentation for any GNU software be a man + page. Write a manual in Texinfo instead. Man pages are just for + the sake of people running GNU software on Unix, which is a secondary application only.* -`manext' +'manext' The file name extension for the installed man page. This should contain a period followed by the appropriate digit; it should - normally be `.1'. + normally be '.1'. -`man1ext' +'man1ext' The file name extension for installed section 1 man pages. - -`man2ext' +'man2ext' The file name extension for installed section 2 man pages. - -`...' - Use these names instead of `manext' if the package needs to - install man pages in more than one section of the manual. +'...' + Use these names instead of 'manext' if the package needs to install + man pages in more than one section of the manual. And finally, you should set the following variable: -`srcdir' +'srcdir' The directory for the sources being compiled. The value of this - variable is normally inserted by the `configure' shell script. - (If you are using Autoconf, use `srcdir = @srcdir@'.) + variable is normally inserted by the 'configure' shell script. (If + you are using Autoconf, use 'srcdir = @srcdir@'.) For example: @@ -4373,7 +4351,7 @@ have Info files, so every program needs `infodir', but not all need If your program installs a large number of files into one of the standard user-specified directories, it might be useful to group them into a subdirectory particular to that program. If you do this, you -should write the `install' rule to create these subdirectories. +should write the 'install' rule to create these subdirectories. Do not expect the user to include the subdirectory name in the value of any of the variables listed above. The idea of having a uniform set @@ -4398,47 +4376,47 @@ File: standards.info, Node: Standard Targets, Next: Install Command Categories All GNU programs should have the following targets in their Makefiles: -`all' +'all' Compile the entire program. This should be the default target. This target need not rebuild any documentation files; Info files should normally be included in the distribution, and DVI (and other documentation format) files should be made only when explicitly asked for. - By default, the Make rules should compile and link with `-g', so + By default, the Make rules should compile and link with '-g', so that executable programs have debugging symbols. Users who don't mind being helpless can strip the executables later if they wish. -`install' +'install' Compile the program and copy the executables, libraries, and so on to the file names where they should reside for actual use. If there is a simple test to verify that a program is properly installed, this target should run that test. Do not strip executables when installing them. Devil-may-care - users can use the `install-strip' target to do that. + users can use the 'install-strip' target to do that. - If possible, write the `install' target rule so that it does not + If possible, write the 'install' target rule so that it does not modify anything in the directory where the program was built, - provided `make all' has just been done. This is convenient for + provided 'make all' has just been done. This is convenient for building the program under one user name and installing it under another. The commands should create all the directories in which files are to be installed, if they don't already exist. This includes the - directories specified as the values of the variables `prefix' and - `exec_prefix', as well as all subdirectories that are needed. One - way to do this is by means of an `installdirs' target as described + directories specified as the values of the variables 'prefix' and + 'exec_prefix', as well as all subdirectories that are needed. One + way to do this is by means of an 'installdirs' target as described below. - Use `-' before any command for installing a man page, so that - `make' will ignore any errors. This is in case there are systems + Use '-' before any command for installing a man page, so that + 'make' will ignore any errors. This is in case there are systems that don't have the Unix man page documentation system installed. - The way to install Info files is to copy them into `$(infodir)' - with `$(INSTALL_DATA)' (*note Command Variables::), and then run - the `install-info' program if it is present. `install-info' is a - program that edits the Info `dir' file to add or update the menu + The way to install Info files is to copy them into '$(infodir)' + with '$(INSTALL_DATA)' (*note Command Variables::), and then run + the 'install-info' program if it is present. 'install-info' is a + program that edits the Info 'dir' file to add or update the menu entry for the given Info file; it is part of the Texinfo package. Here is a sample rule to install an Info file: @@ -4459,47 +4437,47 @@ All GNU programs should have the following targets in their Makefiles: $(DESTDIR)$(infodir)/foo.info; \ else true; fi - When writing the `install' target, you must classify all the + When writing the 'install' target, you must classify all the commands into three categories: normal ones, "pre-installation" commands and "post-installation" commands. *Note Install Command Categories::. -`install-html' -`install-dvi' -`install-pdf' -`install-ps' +'install-html' +'install-dvi' +'install-pdf' +'install-ps' These targets install documentation in formats other than Info; they're intended to be called explicitly by the person installing - the package, if that format is desired. GNU prefers Info files, - so these must be installed by the `install' target. + the package, if that format is desired. GNU prefers Info files, so + these must be installed by the 'install' target. When you have many documentation files to install, we recommend that you avoid collisions and clutter by arranging for these targets to install in subdirectories of the appropriate - installation directory, such as `htmldir'. As one example, if - your package has multiple manuals, and you wish to install HTML + installation directory, such as 'htmldir'. As one example, if your + package has multiple manuals, and you wish to install HTML documentation with many files (such as the "split" mode output by - `makeinfo --html'), you'll certainly want to use subdirectories, - or two nodes with the same name in different manuals will - overwrite each other. + 'makeinfo --html'), you'll certainly want to use subdirectories, or + two nodes with the same name in different manuals will overwrite + each other. - Please make these `install-FORMAT' targets invoke the commands for + Please make these 'install-FORMAT' targets invoke the commands for the FORMAT target, for example, by making FORMAT a dependency. -`uninstall' - Delete all the installed files--the copies that the `install' and - `install-*' targets create. +'uninstall' + Delete all the installed files--the copies that the 'install' and + 'install-*' targets create. This rule should not modify the directories where compilation is done, only the directories where files are installed. - The uninstallation commands are divided into three categories, - just like the installation commands. *Note Install Command + The uninstallation commands are divided into three categories, just + like the installation commands. *Note Install Command Categories::. -`install-strip' - Like `install', but strip the executable files while installing - them. In simple cases, this target can use the `install' target in +'install-strip' + Like 'install', but strip the executable files while installing + them. In simple cases, this target can use the 'install' target in a simple way: install-strip: @@ -4507,105 +4485,106 @@ All GNU programs should have the following targets in their Makefiles: install But if the package installs scripts as well as real executables, - the `install-strip' target can't just refer to the `install' + the 'install-strip' target can't just refer to the 'install' target; it has to strip the executables but not the scripts. - `install-strip' should not strip the executables in the build + 'install-strip' should not strip the executables in the build directory which are being copied for installation. It should only strip the copies that are installed. - Normally we do not recommend stripping an executable unless you - are sure the program has no bugs. However, it can be reasonable - to install a stripped executable for actual execution while saving - the unstripped executable elsewhere in case there is a bug. + Normally we do not recommend stripping an executable unless you are + sure the program has no bugs. However, it can be reasonable to + install a stripped executable for actual execution while saving the + unstripped executable elsewhere in case there is a bug. -`clean' - Delete all files in the current directory that are normally - created by building the program. Also delete files in other - directories if they are created by this makefile. However, don't - delete the files that record the configuration. Also preserve - files that could be made by building, but normally aren't because - the distribution comes with them. There is no need to delete - parent directories that were created with `mkdir -p', since they - could have existed anyway. +'clean' - Delete `.dvi' files here if they are not part of the distribution. + Delete all files in the current directory that are normally created + by building the program. Also delete files in other directories if + they are created by this makefile. However, don't delete the files + that record the configuration. Also preserve files that could be + made by building, but normally aren't because the distribution + comes with them. There is no need to delete parent directories + that were created with 'mkdir -p', since they could have existed + anyway. -`distclean' + Delete '.dvi' files here if they are not part of the distribution. + +'distclean' Delete all files in the current directory (or created by this makefile) that are created by configuring or building the program. If you have unpacked the source and built the program without - creating any other files, `make distclean' should leave only the + creating any other files, 'make distclean' should leave only the files that were in the distribution. However, there is no need to - delete parent directories that were created with `mkdir -p', since + delete parent directories that were created with 'mkdir -p', since they could have existed anyway. -`mostlyclean' - Like `clean', but may refrain from deleting a few files that people - normally don't want to recompile. For example, the `mostlyclean' - target for GCC does not delete `libgcc.a', because recompiling it +'mostlyclean' + Like 'clean', but may refrain from deleting a few files that people + normally don't want to recompile. For example, the 'mostlyclean' + target for GCC does not delete 'libgcc.a', because recompiling it is rarely necessary and takes a lot of time. -`maintainer-clean' +'maintainer-clean' Delete almost everything that can be reconstructed with this Makefile. This typically includes everything deleted by - `distclean', plus more: C source files produced by Bison, tags + 'distclean', plus more: C source files produced by Bison, tags tables, Info files, and so on. The reason we say "almost everything" is that running the command - `make maintainer-clean' should not delete `configure' even if - `configure' can be remade using a rule in the Makefile. More - generally, `make maintainer-clean' should not delete anything that - needs to exist in order to run `configure' and then begin to build + 'make maintainer-clean' should not delete 'configure' even if + 'configure' can be remade using a rule in the Makefile. More + generally, 'make maintainer-clean' should not delete anything that + needs to exist in order to run 'configure' and then begin to build the program. Also, there is no need to delete parent directories - that were created with `mkdir -p', since they could have existed - anyway. These are the only exceptions; `maintainer-clean' should + that were created with 'mkdir -p', since they could have existed + anyway. These are the only exceptions; 'maintainer-clean' should delete everything else that can be rebuilt. - The `maintainer-clean' target is intended to be used by a + The 'maintainer-clean' target is intended to be used by a maintainer of the package, not by ordinary users. You may need - special tools to reconstruct some of the files that `make - maintainer-clean' deletes. Since these files are normally - included in the distribution, we don't take care to make them easy - to reconstruct. If you find you need to unpack the full - distribution again, don't blame us. + special tools to reconstruct some of the files that 'make + maintainer-clean' deletes. Since these files are normally included + in the distribution, we don't take care to make them easy to + reconstruct. If you find you need to unpack the full distribution + again, don't blame us. To help make users aware of this, the commands for the special - `maintainer-clean' target should start with these two: + 'maintainer-clean' target should start with these two: @echo 'This command is intended for maintainers to use; it' @echo 'deletes files that may need special tools to rebuild.' -`TAGS' +'TAGS' Update a tags table for this program. -`info' - Generate any Info files needed. The best way to write the rules - is as follows: +'info' + Generate any Info files needed. The best way to write the rules is + as follows: info: foo.info foo.info: foo.texi chap1.texi chap2.texi $(MAKEINFO) $(srcdir)/foo.texi - You must define the variable `MAKEINFO' in the Makefile. It should - run the `makeinfo' program, which is part of the Texinfo + You must define the variable 'MAKEINFO' in the Makefile. It should + run the 'makeinfo' program, which is part of the Texinfo distribution. Normally a GNU distribution comes with Info files, and that means - the Info files are present in the source directory. Therefore, - the Make rule for an info file should update it in the source + the Info files are present in the source directory. Therefore, the + Make rule for an info file should update it in the source directory. When users build the package, ordinarily Make will not update the Info files because they will already be up to date. -`dvi' -`html' -`pdf' -`ps' +'dvi' +'html' +'pdf' +'ps' Generate documentation files in the given format. These targets should always exist, but any or all can be a no-op if the given output format cannot be generated. These targets should not be - dependencies of the `all' target; the user must manually invoke + dependencies of the 'all' target; the user must manually invoke them. Here's an example rule for generating DVI files from Texinfo: @@ -4615,10 +4594,10 @@ All GNU programs should have the following targets in their Makefiles: foo.dvi: foo.texi chap1.texi chap2.texi $(TEXI2DVI) $(srcdir)/foo.texi - You must define the variable `TEXI2DVI' in the Makefile. It should - run the program `texi2dvi', which is part of the Texinfo + You must define the variable 'TEXI2DVI' in the Makefile. It should + run the program 'texi2dvi', which is part of the Texinfo distribution.(1) Alternatively, write just the dependencies, and - allow GNU `make' to provide the command. + allow GNU 'make' to provide the command. Here's another example, this one for generating HTML from Texinfo: @@ -4627,31 +4606,31 @@ All GNU programs should have the following targets in their Makefiles: foo.html: foo.texi chap1.texi chap2.texi $(TEXI2HTML) $(srcdir)/foo.texi - Again, you would define the variable `TEXI2HTML' in the Makefile; - for example, it might run `makeinfo --no-split --html' (`makeinfo' + Again, you would define the variable 'TEXI2HTML' in the Makefile; + for example, it might run 'makeinfo --no-split --html' ('makeinfo' is part of the Texinfo distribution). -`dist' +'dist' Create a distribution tar file for this program. The tar file should be set up so that the file names in the tar file start with a subdirectory name which is the name of the package it is a distribution for. This name can include the version number. For example, the distribution tar file of GCC version 1.40 unpacks - into a subdirectory named `gcc-1.40'. + into a subdirectory named 'gcc-1.40'. The easiest way to do this is to create a subdirectory - appropriately named, use `ln' or `cp' to install the proper files - in it, and then `tar' that subdirectory. + appropriately named, use 'ln' or 'cp' to install the proper files + in it, and then 'tar' that subdirectory. - Compress the tar file with `gzip'. For example, the actual - distribution file for GCC version 1.40 is called `gcc-1.40.tar.gz'. + Compress the tar file with 'gzip'. For example, the actual + distribution file for GCC version 1.40 is called 'gcc-1.40.tar.gz'. - The `dist' target should explicitly depend on all non-source files + The 'dist' target should explicitly depend on all non-source files that are in the distribution, to make sure they are up to date in the distribution. *Note Making Releases: Releases. -`check' +'check' Perform self-tests (if any). The user must build the program before running the tests, but need not install the program; you should write the self-tests so that they work when the program is @@ -4660,15 +4639,15 @@ All GNU programs should have the following targets in their Makefiles: The following targets are suggested as conventional names, for programs in which they are useful. -`installcheck' +'installcheck' Perform installation tests (if any). The user must build and install the program before running the tests. You should not - assume that `$(bindir)' is in the search path. + assume that '$(bindir)' is in the search path. -`installdirs' - It's useful to add a target named `installdirs' to create the +'installdirs' + It's useful to add a target named 'installdirs' to create the directories where files are installed, and their parent - directories. There is a script called `mkinstalldirs' which is + directories. There is a script called 'mkinstalldirs' which is convenient for this; you can find it in the Texinfo package. You can use a rule like this: @@ -4679,7 +4658,7 @@ programs in which they are useful. $(libdir) $(infodir) \ $(mandir) - or, if you wish to support `DESTDIR', + or, if you wish to support 'DESTDIR', # Make sure all installation directories (e.g. $(bindir)) # actually exist by making them if necessary. @@ -4694,7 +4673,7 @@ programs in which they are useful. ---------- Footnotes ---------- - (1) `texi2dvi' uses TeX to do the real work of formatting. TeX is + (1) 'texi2dvi' uses TeX to do the real work of formatting. TeX is not distributed with Texinfo. @@ -4703,7 +4682,7 @@ File: standards.info, Node: Install Command Categories, Prev: Standard Targets 7.2.7 Install Command Categories -------------------------------- -When writing the `install' target, you must classify all the commands +When writing the 'install' target, you must classify all the commands into three categories: normal ones, "pre-installation" commands and "post-installation" commands. @@ -4720,7 +4699,7 @@ commands, and post-installation commands are typically run after the normal commands. The most common use for a post-installation command is to run -`install-info'. This cannot be done with a normal command, since it +'install-info'. This cannot be done with a normal command, since it alters a file (the Info directory) which does not come entirely and solely from the package being installed. It is a post-installation command because it needs to be done after the normal command which @@ -4729,7 +4708,7 @@ installs the package's Info files. Most programs don't need any pre-installation commands, but we have the feature just in case it is needed. - To classify the commands in the `install' rule into these three + To classify the commands in the 'install' rule into these three categories, insert "category lines" among them. A category line specifies the category for the commands that follow. @@ -4747,12 +4726,12 @@ explains what it means: $(POST_INSTALL) # Post-install commands follow. $(NORMAL_INSTALL) # Normal commands follow. - If you don't use a category line at the beginning of the `install' + If you don't use a category line at the beginning of the 'install' rule, all the commands are classified as normal until the first category line. If you don't use any category lines, all the commands are classified as normal. - These are the category lines for `uninstall': + These are the category lines for 'uninstall': $(PRE_UNINSTALL) # Pre-uninstall commands follow. $(POST_UNINSTALL) # Post-uninstall commands follow. @@ -4761,8 +4740,8 @@ classified as normal. Typically, a pre-uninstall command would be used for deleting entries from the Info directory. - If the `install' or `uninstall' target has any dependencies which -act as subroutines of installation, then you should start _each_ + If the 'install' or 'uninstall' target has any dependencies which act +as subroutines of installation, then you should start _each_ dependency's commands with a category line, and start the main target's commands with a category line also. This way, you can ensure that each command is placed in the right category regardless of which of the @@ -4778,15 +4757,15 @@ programs except for these: test touch true uname xargs yes The reason for distinguishing the commands in this way is for the -sake of making binary packages. Typically a binary package contains -all the executables and other files that need to be installed, and has -its own method of installing them--so it does not need to run the normal +sake of making binary packages. Typically a binary package contains all +the executables and other files that need to be installed, and has its +own method of installing them--so it does not need to run the normal installation commands. But installing the binary package does need to execute the pre-installation and post-installation commands. Programs to build binary packages work by extracting the pre-installation and post-installation commands. Here is one way of -extracting the pre-installation commands (the `-s' option to `make' is +extracting the pre-installation commands (the '-s' option to 'make' is needed to silence messages about entering subdirectories): make -s -n install -o all \ @@ -4795,7 +4774,7 @@ needed to silence messages about entering subdirectories): NORMAL_INSTALL=normal-install \ | gawk -f pre-install.awk -where the file `pre-install.awk' could contain this: +where the file 'pre-install.awk' could contain this: $0 ~ /^(normal-install|post-install)[ \t]*$/ {on = 0} on {print $0} @@ -4807,41 +4786,41 @@ File: standards.info, Node: Releases, Prev: Makefile Conventions, Up: Managin 7.3 Making Releases =================== -You should identify each release with a pair of version numbers, a -major version and a minor. We have no objection to using more than two +You should identify each release with a pair of version numbers, a major +version and a minor. We have no objection to using more than two numbers, but it is very unlikely that you really need them. - Package the distribution of `Foo version 69.96' up in a gzipped tar -file with the name `foo-69.96.tar.gz'. It should unpack into a -subdirectory named `foo-69.96'. + Package the distribution of 'Foo version 69.96' up in a gzipped tar +file with the name 'foo-69.96.tar.gz'. It should unpack into a +subdirectory named 'foo-69.96'. Building and installing the program should never modify any of the -files contained in the distribution. This means that all the files -that form part of the program in any way must be classified into "source +files contained in the distribution. This means that all the files that +form part of the program in any way must be classified into "source files" and "non-source files". Source files are written by humans and never changed automatically; non-source files are produced from source files by programs under the control of the Makefile. - The distribution should contain a file named `README' which gives -the name of the package, and a general description of what it does. It -is also good to explain the purpose of each of the first-level -subdirectories in the package, if there are any. The `README' file + The distribution should contain a file named 'README' which gives the +name of the package, and a general description of what it does. It is +also good to explain the purpose of each of the first-level +subdirectories in the package, if there are any. The 'README' file should either state the version number of the package, or refer to where in the package it can be found. - The `README' file should refer to the file `INSTALL', which should + The 'README' file should refer to the file 'INSTALL', which should contain an explanation of the installation procedure. - The `README' file should also refer to the file which contains the + The 'README' file should also refer to the file which contains the copying conditions. The GNU GPL, if used, should be in a file called -`COPYING'. If the GNU LGPL is used, it should be in a file called -`COPYING.LESSER'. +'COPYING'. If the GNU LGPL is used, it should be in a file called +'COPYING.LESSER'. Naturally, all the source files must be in the distribution. It is okay to include non-source files in the distribution, provided they are up-to-date and machine-independent, so that building the distribution normally will never modify them. We commonly include non-source files -produced by Bison, `lex', TeX, and `makeinfo'; this helps avoid +produced by Bison, 'lex', TeX, and 'makeinfo'; this helps avoid unnecessary dependencies between our distributions, so that users can install whichever packages they want to install. @@ -4851,11 +4830,11 @@ So if you do distribute non-source files, always make sure they are up to date when you make a new distribution. Make sure that all the files in the distribution are world-readable, -and that directories are world-readable and world-searchable (octal -mode 755). We used to recommend that all directories in the -distribution also be world-writable (octal mode 777), because ancient -versions of `tar' would otherwise not cope when extracting the archive -as an unprivileged user. That can easily lead to security issues when +and that directories are world-readable and world-searchable (octal mode +755). We used to recommend that all directories in the distribution +also be world-writable (octal mode 777), because ancient versions of +'tar' would otherwise not cope when extracting the archive as an +unprivileged user. That can easily lead to security issues when creating the archive, however, so now we recommend against that. Don't include any symbolic links in the distribution itself. If the @@ -4864,15 +4843,15 @@ systems that don't support symbolic links. Also, don't use multiple names for one file in different directories, because certain file systems cannot handle this and that prevents unpacking the distribution. - Try to make sure that all the file names will be unique on MS-DOS. A + Try to make sure that all the file names will be unique on MS-DOS. A name on MS-DOS consists of up to 8 characters, optionally followed by a period and up to three characters. MS-DOS will truncate extra -characters both before and after the period. Thus, `foobarhacker.c' -and `foobarhacker.o' are not ambiguous; they are truncated to -`foobarha.c' and `foobarha.o', which are distinct. +characters both before and after the period. Thus, 'foobarhacker.c' and +'foobarhacker.o' are not ambiguous; they are truncated to 'foobarha.c' +and 'foobarha.o', which are distinct. - Include in your distribution a copy of the `texinfo.tex' you used to -test print any `*.texinfo' or `*.texi' files. + Include in your distribution a copy of the 'texinfo.tex' you used to +test print any '*.texinfo' or '*.texi' files. Likewise, if your program uses small GNU software packages like regex, getopt, obstack, or termcap, include them in the distribution @@ -4888,28 +4867,28 @@ File: standards.info, Node: References, Next: GNU Free Documentation License, A GNU program should not recommend, promote, or grant legitimacy to the use of any non-free program. Proprietary software is a social and -ethical problem, and our aim is to put an end to that problem. We -can't stop some people from writing proprietary programs, or stop other -people from using them, but we can and should refuse to advertise them -to new potential customers, or to give the public the idea that their -existence is ethical. +ethical problem, and our aim is to put an end to that problem. We can't +stop some people from writing proprietary programs, or stop other people +from using them, but we can and should refuse to advertise them to new +potential customers, or to give the public the idea that their existence +is ethical. The GNU definition of free software is found on the GNU web site at -`http://www.gnu.org/philosophy/free-sw.html', and the definition of -free documentation is found at -`http://www.gnu.org/philosophy/free-doc.html'. The terms "free" and -"non-free", used in this document, refer to those definitions. +<http://www.gnu.org/philosophy/free-sw.html>, and the definition of free +documentation is found at <http://www.gnu.org/philosophy/free-doc.html>. +The terms "free" and "non-free", used in this document, refer to those +definitions. A list of important licenses and whether they qualify as free is in -`http://www.gnu.org/licenses/license-list.html'. If it is not clear +<http://www.gnu.org/licenses/license-list.html>. If it is not clear whether a license qualifies as free, please ask the GNU Project by writing to <licensing@gnu.org>. We will answer, and if the license is an important one, we will add it to the list. When a non-free program or system is well known, you can mention it in passing--that is harmless, since users who might want to use it -probably already know about it. For instance, it is fine to explain -how to build your package on top of some widely used non-free operating +probably already know about it. For instance, it is fine to explain how +to build your package on top of some widely used non-free operating system, or how to use it together with some widely used non-free program. @@ -4918,8 +4897,8 @@ who already use the non-free program to use your program with it--don't give, or refer to, any further information about the proprietary program, and don't imply that the proprietary program enhances your program, or that its existence is in any way a good thing. The goal -should be that people already using the proprietary program will get -the advice they need about how to use your free program with it, while +should be that people already using the proprietary program will get the +advice they need about how to use your free program with it, while people who don't already use the proprietary program will not see anything likely to lead them to take an interest in it. @@ -4944,30 +4923,30 @@ recommend, promote or legitimize programs that depend on non-free software to run. Some free programs strongly encourage the use of non-free software. -A typical example is `mplayer'. It is free software in itself, and the -free code can handle some kinds of files. However, `mplayer' -recommends use of non-free codecs for other kinds of files, and users -that install `mplayer' are very likely to install those codecs along -with it. To recommend `mplayer' is, in effect, to promote use of the -non-free codecs. +A typical example is 'mplayer'. It is free software in itself, and the +free code can handle some kinds of files. However, 'mplayer' recommends +use of non-free codecs for other kinds of files, and users that install +'mplayer' are very likely to install those codecs along with it. To +recommend 'mplayer' is, in effect, to promote use of the non-free +codecs. Thus, you should not recommend programs that strongly encourage the -use of non-free software. This is why we do not list `mplayer' in the +use of non-free software. This is why we do not list 'mplayer' in the Free Software Directory. A GNU package should not refer the user to any non-free documentation for free software. Free documentation that can be included in free operating systems is essential for completing the GNU system, or any -free operating system, so encouraging it is a priority; to recommend -use of documentation that we are not allowed to include undermines the +free operating system, so encouraging it is a priority; to recommend use +of documentation that we are not allowed to include undermines the impetus for the community to produce documentation that we can include. So GNU packages should never recommend non-free documentation. By contrast, it is ok to refer to journal articles and textbooks in the comments of a program for explanation of how it functions, even though they are non-free. This is because we don't include such things -in the GNU system even they are free--they are outside the scope of -what a software distribution needs to include. +in the GNU system even they are free--they are outside the scope of what +a software distribution needs to include. Referring to a web site that describes or recommends a non-free program is promoting that program, so please do not make links (or @@ -4986,8 +4965,8 @@ recommends AT&T's non-free software packages; you should not refer to a site that links to AT&T's site presenting it as a place to get some non-free program, because that link recommends and legitimizes the non-free program. However, that a site contains a link to AT&T's web -site for some other purpose (such as long-distance telephone service) -is not an objection against it. +site for some other purpose (such as long-distance telephone service) is +not an objection against it. File: standards.info, Node: GNU Free Documentation License, Next: Index, Prev: References, Up: Top @@ -4998,7 +4977,7 @@ Appendix A GNU Free Documentation License Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. - `http://fsf.org/' + <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @@ -5023,21 +5002,21 @@ Appendix A GNU Free Documentation License 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 + 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 + 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. + 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 @@ -5055,12 +5034,12 @@ Appendix A GNU Free Documentation License 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. + 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 @@ -5071,27 +5050,27 @@ Appendix A GNU Free Documentation License 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". + 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. + 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 @@ -5129,8 +5108,8 @@ Appendix A GNU Free Documentation License 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. + 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. @@ -5144,12 +5123,11 @@ Appendix A GNU Free Documentation License 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. + 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 @@ -5157,40 +5135,39 @@ Appendix A GNU Free Documentation License 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. + 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. + 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: + 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. + 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 @@ -5220,31 +5197,30 @@ Appendix A GNU Free Documentation License 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. + 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. + 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 + 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. + 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. @@ -5257,11 +5233,11 @@ Appendix A GNU Free Documentation License 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. + 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 @@ -5270,15 +5246,15 @@ Appendix A GNU Free Documentation License 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. + 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 @@ -5288,8 +5264,8 @@ Appendix A GNU Free Documentation License 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, + 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. @@ -5316,20 +5292,20 @@ Appendix A GNU Free Documentation License 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. + 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. + 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 + 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 @@ -5374,8 +5350,8 @@ Appendix A GNU Free Documentation 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 + 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. @@ -5387,33 +5363,33 @@ Appendix A GNU Free Documentation License 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. + 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 + 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/'. + <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 + 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 + 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also @@ -5443,7 +5419,6 @@ Appendix A GNU Free Documentation License 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 ==================================================== @@ -5460,7 +5435,7 @@ notices just after the title page: Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover -Texts, replace the "with...Texts." line with this: +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 @@ -5471,9 +5446,9 @@ 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. +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: standards.info, Node: Index, Prev: GNU Free Documentation License, Up: Top @@ -5484,10 +5459,10 @@ Index * Menu: -* #endif, commenting: Comments. (line 60) -* --help output: --help. (line 6) -* --version output: --version. (line 6) -* -Wall compiler option: Syntactic Conventions. +* '#endif', commenting: Comments. (line 60) +* '--help' output: --help. (line 6) +* '--version' output: --version. (line 6) +* '-Wall' compiler option: Syntactic Conventions. (line 10) * accepting contributions: Contributions. (line 6) * address for bug reports: --help. (line 11) @@ -5503,9 +5478,9 @@ Index * bindir: Directory Variables. (line 54) * braces, in C source: Formatting. (line 6) * bug reports: --help. (line 11) -* bug-standards@gnu.org email address: Preface. (line 30) +* 'bug-standards@gnu.org' email address: Preface. (line 30) * canonical name of a program: --version. (line 12) -* casting pointers to integers: CPU Portability. (line 89) +* casting pointers to integers: CPU Portability. (line 88) * CGI programs, standard options for: Command-Line Interfaces. (line 31) * change logs: Change Logs. (line 6) @@ -5558,16 +5533,16 @@ Index (line 6) * GNOME: Graphical Interfaces. (line 16) -* GNOME and Guile: Source Language. (line 38) +* GNOME and Guile: Source Language. (line 37) * gnustandards project repository: Preface. (line 30) -* gnustandards-commit@gnu.org mailing list: Preface. (line 24) +* 'gnustandards-commit@gnu.org' mailing list: Preface. (line 24) * graphical user interface: Graphical Interfaces. (line 6) * grave accent: Quote Characters. (line 6) * GTK+: Graphical Interfaces. (line 6) -* Guile: Source Language. (line 38) -* implicit int: Syntactic Conventions. +* Guile: Source Language. (line 37) +* implicit 'int': Syntactic Conventions. (line 6) * impossible conditions: Semantics. (line 70) * installations, staged: DESTDIR. (line 6) @@ -5595,7 +5570,7 @@ Index (line 12) * makefile, conventions for: Makefile Conventions. (line 6) -* malloc return value: Semantics. (line 25) +* 'malloc' return value: Semantics. (line 25) * man pages: Man Pages. (line 6) * manual structure: Manual Structure Details. (line 6) @@ -5607,14 +5582,14 @@ Index * multiple variables in a line: Syntactic Conventions. (line 35) * names of variables, functions, and files: Names. (line 6) -* NEWS file: NEWS File. (line 6) +* 'NEWS' file: NEWS File. (line 6) * non-ASCII characters: Character Set. (line 6) * non-POSIX systems, and portability: System Portability. (line 32) * non-standard extensions: Using Extensions. (line 6) -* NUL characters: Semantics. (line 11) +* 'NUL' characters: Semantics. (line 11) * OID allocations for GNU: OID Allocations. (line 6) * open brace: Formatting. (line 6) -* optional features, configure-time: Configuration. (line 100) +* optional features, configure-time: Configuration. (line 97) * options for compatibility: Compatibility. (line 14) * options, standard command-line: Command-Line Interfaces. (line 31) @@ -5626,7 +5601,7 @@ Index * portability, and library functions: System Functions. (line 6) * portability, between system types: System Portability. (line 6) * POSIX compatibility: Compatibility. (line 6) -* POSIXLY_CORRECT, environment variable: Compatibility. (line 21) +* 'POSIXLY_CORRECT', environment variable: Compatibility. (line 21) * post-installation commands: Install Command Categories. (line 6) * pre-installation commands: Install Command Categories. @@ -5640,7 +5615,7 @@ Index * proprietary programs: Reading Non-Free Code. (line 6) * quote characters: Quote Characters. (line 6) -* README file: Releases. (line 21) +* 'README' file: Releases. (line 21) * references to non-free material: References. (line 6) * releasing: Managing Releases. (line 6) * Savannah repository for gnustandards: Preface. (line 30) @@ -5653,92 +5628,92 @@ Index (line 31) * standards for makefiles: Makefile Conventions. (line 6) -* string library functions: System Functions. (line 55) +* string library functions: System Functions. (line 54) * syntactic conventions: Syntactic Conventions. (line 6) * table of long options: Option Table. (line 6) * temporary files: Semantics. (line 84) * temporary variables: Syntactic Conventions. (line 23) -* texinfo.tex, in a distribution: Releases. (line 70) -* TMPDIR environment variable: Semantics. (line 84) +* 'texinfo.tex', in a distribution: Releases. (line 70) +* 'TMPDIR' environment variable: Semantics. (line 84) * trademarks: Trademarks. (line 6) * user interface styles: Graphical Interfaces. (line 6) -* where to obtain standards.texi: Preface. (line 14) +* where to obtain 'standards.texi': Preface. (line 14) * X.509: OID Allocations. (line 6) Tag Table: -Node: Top930 -Node: Preface2205 -Node: Legal Issues4918 -Node: Reading Non-Free Code5388 -Node: Contributions7118 -Node: Trademarks9356 -Node: Design Advice10991 -Node: Source Language11583 -Node: Compatibility13709 -Node: Using Extensions15337 -Node: Standard C16913 -Node: Conditional Compilation19316 -Node: Program Behavior20714 -Node: Non-GNU Standards21830 -Node: Semantics24111 -Node: Libraries28831 -Node: Errors30076 -Node: User Interfaces32569 -Node: Graphical Interfaces34174 -Node: Command-Line Interfaces35358 -Node: --version37390 -Node: --help43127 -Node: Option Table44000 -Node: OID Allocations58955 -Node: Memory Usage60752 -Node: File Usage61788 -Node: Writing C62538 -Node: Formatting63510 -Node: Comments67799 -Node: Syntactic Conventions71351 -Node: Names74813 -Node: System Portability77025 -Node: CPU Portability79916 -Node: System Functions83817 -Node: Internationalization89014 -Node: Character Set93008 -Node: Quote Characters93821 -Node: Mmap95341 -Node: Documentation96049 -Node: GNU Manuals97155 -Node: Doc Strings and Manuals102893 -Node: Manual Structure Details104446 -Node: License for Manuals105864 -Node: Manual Credits106838 -Node: Printed Manuals107231 -Node: NEWS File107917 -Node: Change Logs108595 -Node: Change Log Concepts109349 -Node: Style of Change Logs111452 -Node: Simple Changes113952 -Node: Conditional Changes115394 -Node: Indicating the Part Changed116816 -Node: Man Pages117343 -Node: Reading other Manuals119549 -Node: Managing Releases120340 -Node: Configuration121121 -Node: Makefile Conventions129786 -Node: Makefile Basics130668 -Node: Utilities in Makefiles133842 -Node: Command Variables135987 -Node: DESTDIR139209 -Node: Directory Variables141358 -Node: Standard Targets155851 -Ref: Standard Targets-Footnote-1169366 -Node: Install Command Categories169466 -Node: Releases173999 -Node: References178004 -Node: GNU Free Documentation License183851 -Node: Index209018 +Node: Top808 +Node: Preface2083 +Node: Legal Issues4784 +Node: Reading Non-Free Code5254 +Node: Contributions6983 +Node: Trademarks9221 +Node: Design Advice10855 +Node: Source Language11447 +Node: Compatibility13566 +Node: Using Extensions15194 +Node: Standard C16771 +Node: Conditional Compilation19174 +Node: Program Behavior20572 +Node: Non-GNU Standards21688 +Node: Semantics23969 +Node: Libraries28689 +Node: Errors29934 +Node: User Interfaces32427 +Node: Graphical Interfaces34032 +Node: Command-Line Interfaces35215 +Node: --version37245 +Node: --help42964 +Node: Option Table43837 +Node: OID Allocations58792 +Node: Memory Usage60589 +Node: File Usage61625 +Node: Writing C62375 +Node: Formatting63345 +Node: Comments67634 +Node: Syntactic Conventions71185 +Node: Names74647 +Node: System Portability76859 +Node: CPU Portability79750 +Node: System Functions83652 +Node: Internationalization88844 +Node: Character Set92838 +Node: Quote Characters93651 +Node: Mmap95171 +Node: Documentation95879 +Node: GNU Manuals96985 +Node: Doc Strings and Manuals102723 +Node: Manual Structure Details104276 +Node: License for Manuals105694 +Node: Manual Credits106667 +Node: Printed Manuals107060 +Node: NEWS File107746 +Node: Change Logs108424 +Node: Change Log Concepts109178 +Node: Style of Change Logs111281 +Node: Simple Changes113781 +Node: Conditional Changes115223 +Node: Indicating the Part Changed116645 +Node: Man Pages117172 +Node: Reading other Manuals119346 +Node: Managing Releases120137 +Node: Configuration120917 +Node: Makefile Conventions129580 +Node: Makefile Basics130462 +Node: Utilities in Makefiles133636 +Node: Command Variables135782 +Node: DESTDIR139005 +Node: Directory Variables141154 +Node: Standard Targets155639 +Ref: Standard Targets-Footnote-1169155 +Node: Install Command Categories169256 +Node: Releases173789 +Node: References177793 +Node: GNU Free Documentation License183639 +Node: Index208786 End Tag Table diff --git a/share/man/man1/aarch64-linux-android-addr2line.1 b/share/man/man1/aarch64-linux-android-addr2line.1 index f55eee6..d583a40 100644 --- a/share/man/man1/aarch64-linux-android-addr2line.1 +++ b/share/man/man1/aarch64-linux-android-addr2line.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "ADDR2LINE 1" -.TH ADDR2LINE 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH ADDR2LINE 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-ar.1 b/share/man/man1/aarch64-linux-android-ar.1 index 32b7a63..a113d3c 100644 --- a/share/man/man1/aarch64-linux-android-ar.1 +++ b/share/man/man1/aarch64-linux-android-ar.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "AR 1" -.TH AR 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH AR 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-as.1 b/share/man/man1/aarch64-linux-android-as.1 index 012a58a..98e4722 100644 --- a/share/man/man1/aarch64-linux-android-as.1 +++ b/share/man/man1/aarch64-linux-android-as.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "AS 1" -.TH AS 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH AS 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-c++filt.1 b/share/man/man1/aarch64-linux-android-c++filt.1 index 6cba38e..51e7137 100644 --- a/share/man/man1/aarch64-linux-android-c++filt.1 +++ b/share/man/man1/aarch64-linux-android-c++filt.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "C++FILT 1" -.TH C++FILT 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH C++FILT 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-dlltool.1 b/share/man/man1/aarch64-linux-android-dlltool.1 index 9f9d527..fc3718a 100644 --- a/share/man/man1/aarch64-linux-android-dlltool.1 +++ b/share/man/man1/aarch64-linux-android-dlltool.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "DLLTOOL 1" -.TH DLLTOOL 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH DLLTOOL 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-elfedit.1 b/share/man/man1/aarch64-linux-android-elfedit.1 index 2db21cc..5b29d79 100644 --- a/share/man/man1/aarch64-linux-android-elfedit.1 +++ b/share/man/man1/aarch64-linux-android-elfedit.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "ELFEDIT 1" -.TH ELFEDIT 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH ELFEDIT 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-gprof.1 b/share/man/man1/aarch64-linux-android-gprof.1 index 2e7fcb6..2ae6efc 100644 --- a/share/man/man1/aarch64-linux-android-gprof.1 +++ b/share/man/man1/aarch64-linux-android-gprof.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "GPROF 1" -.TH GPROF 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU" +.TH GPROF 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-ld.1 b/share/man/man1/aarch64-linux-android-ld.1 index 71edcde..5b65dc0 100644 --- a/share/man/man1/aarch64-linux-android-ld.1 +++ b/share/man/man1/aarch64-linux-android-ld.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "LD 1" -.TH LD 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH LD 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-nlmconv.1 b/share/man/man1/aarch64-linux-android-nlmconv.1 index 0cb8e48..ef3de1e 100644 --- a/share/man/man1/aarch64-linux-android-nlmconv.1 +++ b/share/man/man1/aarch64-linux-android-nlmconv.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "NLMCONV 1" -.TH NLMCONV 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH NLMCONV 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-nm.1 b/share/man/man1/aarch64-linux-android-nm.1 index 981a122..9a721a9 100644 --- a/share/man/man1/aarch64-linux-android-nm.1 +++ b/share/man/man1/aarch64-linux-android-nm.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "NM 1" -.TH NM 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH NM 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-objcopy.1 b/share/man/man1/aarch64-linux-android-objcopy.1 index ce089dd..e2a87f9 100644 --- a/share/man/man1/aarch64-linux-android-objcopy.1 +++ b/share/man/man1/aarch64-linux-android-objcopy.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "OBJCOPY 1" -.TH OBJCOPY 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH OBJCOPY 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-objdump.1 b/share/man/man1/aarch64-linux-android-objdump.1 index 25507aa..1582825 100644 --- a/share/man/man1/aarch64-linux-android-objdump.1 +++ b/share/man/man1/aarch64-linux-android-objdump.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "OBJDUMP 1" -.TH OBJDUMP 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH OBJDUMP 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-ranlib.1 b/share/man/man1/aarch64-linux-android-ranlib.1 index 2026815..3b5252e 100644 --- a/share/man/man1/aarch64-linux-android-ranlib.1 +++ b/share/man/man1/aarch64-linux-android-ranlib.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "RANLIB 1" -.TH RANLIB 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH RANLIB 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-readelf.1 b/share/man/man1/aarch64-linux-android-readelf.1 index 4679a05..e468718 100644 --- a/share/man/man1/aarch64-linux-android-readelf.1 +++ b/share/man/man1/aarch64-linux-android-readelf.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "READELF 1" -.TH READELF 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH READELF 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-size.1 b/share/man/man1/aarch64-linux-android-size.1 index fcfc261..8b47bc9 100644 --- a/share/man/man1/aarch64-linux-android-size.1 +++ b/share/man/man1/aarch64-linux-android-size.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "SIZE 1" -.TH SIZE 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH SIZE 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-strings.1 b/share/man/man1/aarch64-linux-android-strings.1 index 9efb303..0852b04 100644 --- a/share/man/man1/aarch64-linux-android-strings.1 +++ b/share/man/man1/aarch64-linux-android-strings.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "STRINGS 1" -.TH STRINGS 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH STRINGS 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-strip.1 b/share/man/man1/aarch64-linux-android-strip.1 index ca53e92..b5477df 100644 --- a/share/man/man1/aarch64-linux-android-strip.1 +++ b/share/man/man1/aarch64-linux-android-strip.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "STRIP 1" -.TH STRIP 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH STRIP 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-windmc.1 b/share/man/man1/aarch64-linux-android-windmc.1 index bcf9070..05243e2 100644 --- a/share/man/man1/aarch64-linux-android-windmc.1 +++ b/share/man/man1/aarch64-linux-android-windmc.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "WINDMC 1" -.TH WINDMC 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH WINDMC 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-linux-android-windres.1 b/share/man/man1/aarch64-linux-android-windres.1 index 42e8b00..e654954 100644 --- a/share/man/man1/aarch64-linux-android-windres.1 +++ b/share/man/man1/aarch64-linux-android-windres.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "WINDRES 1" -.TH WINDRES 1 "2014-08-16" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH WINDRES 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-addr2line.1 b/share/man/man1/aarch64-none-elf-addr2line.1 index f878b19..d583a40 100644 --- a/share/man/man1/aarch64-none-elf-addr2line.1 +++ b/share/man/man1/aarch64-none-elf-addr2line.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "ADDR2LINE 1" -.TH ADDR2LINE 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH ADDR2LINE 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-ar.1 b/share/man/man1/aarch64-none-elf-ar.1 index e795752..a113d3c 100644 --- a/share/man/man1/aarch64-none-elf-ar.1 +++ b/share/man/man1/aarch64-none-elf-ar.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "AR 1" -.TH AR 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH AR 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-as.1 b/share/man/man1/aarch64-none-elf-as.1 index 5793922..98e4722 100644 --- a/share/man/man1/aarch64-none-elf-as.1 +++ b/share/man/man1/aarch64-none-elf-as.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "AS 1" -.TH AS 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH AS 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-c++filt.1 b/share/man/man1/aarch64-none-elf-c++filt.1 index ec18619..51e7137 100644 --- a/share/man/man1/aarch64-none-elf-c++filt.1 +++ b/share/man/man1/aarch64-none-elf-c++filt.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "C++FILT 1" -.TH C++FILT 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH C++FILT 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-cpp.1 b/share/man/man1/aarch64-none-elf-cpp.1 index 981e377..4127c82 100644 --- a/share/man/man1/aarch64-none-elf-cpp.1 +++ b/share/man/man1/aarch64-none-elf-cpp.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "CPP 1" -.TH CPP 1 "2014-05-29" "gcc-4.9.1" "GNU" +.TH CPP 1 "2014-08-11" "gcc-4.9.2" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-dlltool.1 b/share/man/man1/aarch64-none-elf-dlltool.1 index 9c63aad..fc3718a 100644 --- a/share/man/man1/aarch64-none-elf-dlltool.1 +++ b/share/man/man1/aarch64-none-elf-dlltool.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "DLLTOOL 1" -.TH DLLTOOL 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH DLLTOOL 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-elfedit.1 b/share/man/man1/aarch64-none-elf-elfedit.1 index e8d9eb8..5b29d79 100644 --- a/share/man/man1/aarch64-none-elf-elfedit.1 +++ b/share/man/man1/aarch64-none-elf-elfedit.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "ELFEDIT 1" -.TH ELFEDIT 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH ELFEDIT 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-g++.1 b/share/man/man1/aarch64-none-elf-g++.1 index 1c709a9..df741e2 100644 --- a/share/man/man1/aarch64-none-elf-g++.1 +++ b/share/man/man1/aarch64-none-elf-g++.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "GCC 1" -.TH GCC 1 "2014-05-29" "gcc-4.9.1" "GNU" +.TH GCC 1 "2014-08-11" "gcc-4.9.2" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-gcc.1 b/share/man/man1/aarch64-none-elf-gcc.1 index 1c709a9..df741e2 100644 --- a/share/man/man1/aarch64-none-elf-gcc.1 +++ b/share/man/man1/aarch64-none-elf-gcc.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "GCC 1" -.TH GCC 1 "2014-05-29" "gcc-4.9.1" "GNU" +.TH GCC 1 "2014-08-11" "gcc-4.9.2" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-gcov.1 b/share/man/man1/aarch64-none-elf-gcov.1 index f5feb94..be735d9 100644 --- a/share/man/man1/aarch64-none-elf-gcov.1 +++ b/share/man/man1/aarch64-none-elf-gcov.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "GCOV 1" -.TH GCOV 1 "2014-05-29" "gcc-4.9.1" "GNU" +.TH GCOV 1 "2014-08-11" "gcc-4.9.2" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-gprof.1 b/share/man/man1/aarch64-none-elf-gprof.1 index 5cd9daa..2ae6efc 100644 --- a/share/man/man1/aarch64-none-elf-gprof.1 +++ b/share/man/man1/aarch64-none-elf-gprof.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "GPROF 1" -.TH GPROF 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU" +.TH GPROF 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-ld.1 b/share/man/man1/aarch64-none-elf-ld.1 index 3c202d4..5b65dc0 100644 --- a/share/man/man1/aarch64-none-elf-ld.1 +++ b/share/man/man1/aarch64-none-elf-ld.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "LD 1" -.TH LD 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH LD 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-nlmconv.1 b/share/man/man1/aarch64-none-elf-nlmconv.1 index 216473e..ef3de1e 100644 --- a/share/man/man1/aarch64-none-elf-nlmconv.1 +++ b/share/man/man1/aarch64-none-elf-nlmconv.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "NLMCONV 1" -.TH NLMCONV 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH NLMCONV 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-nm.1 b/share/man/man1/aarch64-none-elf-nm.1 index c2b3011..9a721a9 100644 --- a/share/man/man1/aarch64-none-elf-nm.1 +++ b/share/man/man1/aarch64-none-elf-nm.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "NM 1" -.TH NM 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH NM 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-objcopy.1 b/share/man/man1/aarch64-none-elf-objcopy.1 index 6cef7e7..e2a87f9 100644 --- a/share/man/man1/aarch64-none-elf-objcopy.1 +++ b/share/man/man1/aarch64-none-elf-objcopy.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "OBJCOPY 1" -.TH OBJCOPY 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH OBJCOPY 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-objdump.1 b/share/man/man1/aarch64-none-elf-objdump.1 index c82ebdd..1582825 100644 --- a/share/man/man1/aarch64-none-elf-objdump.1 +++ b/share/man/man1/aarch64-none-elf-objdump.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "OBJDUMP 1" -.TH OBJDUMP 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH OBJDUMP 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-ranlib.1 b/share/man/man1/aarch64-none-elf-ranlib.1 index ddba937..3b5252e 100644 --- a/share/man/man1/aarch64-none-elf-ranlib.1 +++ b/share/man/man1/aarch64-none-elf-ranlib.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "RANLIB 1" -.TH RANLIB 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH RANLIB 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-readelf.1 b/share/man/man1/aarch64-none-elf-readelf.1 index 71d10c1..e468718 100644 --- a/share/man/man1/aarch64-none-elf-readelf.1 +++ b/share/man/man1/aarch64-none-elf-readelf.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "READELF 1" -.TH READELF 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH READELF 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-size.1 b/share/man/man1/aarch64-none-elf-size.1 index 69996f1..8b47bc9 100644 --- a/share/man/man1/aarch64-none-elf-size.1 +++ b/share/man/man1/aarch64-none-elf-size.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "SIZE 1" -.TH SIZE 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH SIZE 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-strings.1 b/share/man/man1/aarch64-none-elf-strings.1 index 5fd3a1f..0852b04 100644 --- a/share/man/man1/aarch64-none-elf-strings.1 +++ b/share/man/man1/aarch64-none-elf-strings.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "STRINGS 1" -.TH STRINGS 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH STRINGS 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-strip.1 b/share/man/man1/aarch64-none-elf-strip.1 index a3e3c78..b5477df 100644 --- a/share/man/man1/aarch64-none-elf-strip.1 +++ b/share/man/man1/aarch64-none-elf-strip.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "STRIP 1" -.TH STRIP 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH STRIP 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-windmc.1 b/share/man/man1/aarch64-none-elf-windmc.1 index a91d472..05243e2 100644 --- a/share/man/man1/aarch64-none-elf-windmc.1 +++ b/share/man/man1/aarch64-none-elf-windmc.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "WINDMC 1" -.TH WINDMC 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH WINDMC 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff --git a/share/man/man1/aarch64-none-elf-windres.1 b/share/man/man1/aarch64-none-elf-windres.1 index f310b4e..e654954 100644 --- a/share/man/man1/aarch64-none-elf-windres.1 +++ b/share/man/man1/aarch64-none-elf-windres.1 @@ -124,7 +124,7 @@ .\" ======================================================================== .\" .IX Title "WINDRES 1" -.TH WINDRES 1 "2014-06-12" "binutils-2.23.52.0.2" "GNU Development Tools" +.TH WINDRES 1 "2014-08-21" "binutils-2.23.52.0.2" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l |