Remove --enable-omitfp support

This commit is contained in:
Ulrich Drepper 2012-01-07 11:29:31 -05:00
parent d75a0a62b1
commit bdeba1354b
10 changed files with 17 additions and 82 deletions

View File

@ -1,5 +1,12 @@
2012-01-07 Ulrich Drepper <drepper@gmail.com>
[BZ #13552]
* configure.in: Remove --enable-omitfp support.
* FAQ.in: Adjust.
* config.make.in: Likewise.
* Makeconfig: Likewise.
* manual/install.texi: Likewise.
In case anyone cares, the IA-64 architecture could move to ports.
* sysdeps/ia64/*: Removed.
* sysdeps/unix/sysv/linux/ia64/*: Removed.

16
FAQ
View File

@ -464,21 +464,7 @@ any other link path.
1.15. What's the problem with configure --enable-omitfp?
{AJ} When --enable-omitfp is set the libraries are built without frame
pointers. Some compilers produce buggy code for this model and therefore we
don't advise using it at the moment.
If you use --enable-omitfp, you're on your own. If you encounter problems
with a library that was build this way, we advise you to rebuild the library
without --enable-omitfp. If the problem vanishes consider tracking the
problem down and report it as compiler failure.
Since a library built with --enable-omitfp is undebuggable on most systems,
debuggable libraries are also built - you can use them by appending "_g" to
the library names.
The compilation of these extra libraries and the compiler optimizations slow
down the build process and need more disk space.
{} Removed. Does not apply anymore.
1.16. I get failures during `make check'. What should I do?

16
FAQ.in
View File

@ -265,21 +265,7 @@ any other link path.
?? What's the problem with configure --enable-omitfp?
{AJ} When --enable-omitfp is set the libraries are built without frame
pointers. Some compilers produce buggy code for this model and therefore we
don't advise using it at the moment.
If you use --enable-omitfp, you're on your own. If you encounter problems
with a library that was build this way, we advise you to rebuild the library
without --enable-omitfp. If the problem vanishes consider tracking the
problem down and report it as compiler failure.
Since a library built with --enable-omitfp is undebuggable on most systems,
debuggable libraries are also built - you can use them by appending "_g" to
the library names.
The compilation of these extra libraries and the compiler optimizations slow
down the build process and need more disk space.
{} Removed. Does not apply anymore.
?? I get failures during `make check'. What should I do?

20
INSTALL
View File

@ -113,14 +113,6 @@ will be used, and CFLAGS sets optimization options for the compiler.
Don't build libraries with profiling information. You may want to
use this option if you don't plan to do profiling.
`--enable-omitfp'
Use maximum optimization for the normal (static and shared)
libraries, and compile separate static libraries with debugging
information and no optimization. We recommend not doing this.
The extra optimization doesn't gain you much, it may provoke
compiler bugs, and you won't be able to trace bugs through the C
library.
`--disable-versioning'
Don't compile the shared libraries with symbol version information.
Doing this will make the resulting library incompatible with old
@ -204,9 +196,9 @@ cross-compiler for the target you configured the library for; it is
important to use this same `CC' value when running `configure', like
this: `CC=TARGET-gcc configure TARGET'. Set `BUILD_CC' to the compiler
to use for programs run on the build system as part of compiling the
library. You may need to set `AR' and `RANLIB' to cross-compiling
versions of `ar' and `ranlib' if the native tools are not configured to
work with object files for the target you configured for.
library. You may need to set `AR' to cross-compiling versions of `ar'
if the native tools are not configured to work with object files for
the target you configured for.
Installing the C Library
========================
@ -317,12 +309,11 @@ build the GNU C library:
Check the FAQ for any special compiler issues on particular
platforms.
* GNU `binutils'
* GNU `binutils' 2.15 or later
You must use GNU `binutils' (as and ld) to build the GNU C library.
No other assembler or linker has the necessary functionality at the
moment. The configure scripts checks for the appropriate version
for the platform. Too-old versions will prevent building glibc.
moment.
* GNU `texinfo' 3.12f
@ -461,3 +452,4 @@ or the manual has a bug, so report the disagreement. If you find any
errors or omissions in this manual, please report them to the bug
database. If you refer to specific sections of the manual, please
include the section names for easier identification.

View File

@ -1,4 +1,4 @@
# Copyright (C) 1991-2003,2004,2005,2006,2007,2008,2009,2010,2011
# Copyright (C) 1991-2003,2004,2005,2006,2007,2008,2009,2010,2011,2012
# Free Software Foundation, Inc.
# This file is part of the GNU C Library.
@ -762,17 +762,6 @@ CPPFLAGS-.op = -DPROF $(pic-default)
CFLAGS-.op = -pg
libtype.op = lib%_p.a
endif
ifeq (yes,$(build-omitfp))
# Under --enable-omitfp, we build the library optimized without
# debugging information using -fomit-frame-pointer, and build an extra
# library with debugging information. The debuggable objects are named foo.og.
object-suffixes += .og
CPPFLAGS-.og = $(pic-default)
CFLAGS-.og = -g
CFLAGS-.o = $(filter %frame-pointer,$(+cflags)) -g0 -O99 -fomit-frame-pointer -D__USE_STRING_INLINES
CFLAGS-.os += -g0 -O99 -fomit-frame-pointer -D__USE_STRING_INLINES
libtype.og = lib%_g.a
endif
bppfx = BP-
ifeq (yes,$(build-bounded))

2
NEWS
View File

@ -9,7 +9,7 @@ Version 2.16
* The following bugs are resolved with this release:
13526, 13527, 13528, 13529, 13531, 13532, 13533, 13547, 13555
13526, 13527, 13528, 13529, 13531, 13532, 13533, 13547, 13552, 13555
* ISO C11 support:

View File

@ -93,7 +93,6 @@ build-static = @static@
build-shared = @shared@
build-pic-default= @libc_cv_pic_default@
build-profile = @profile@
build-omitfp = @omitfp@
build-bounded = @bounded@
build-static-nss = @static_nss@
add-ons = @add_ons@

11
configure vendored
View File

@ -612,7 +612,6 @@ DEFINES
nopic_initfini
static_nss
bounded
omitfp
profile
libc_cv_pic_default
shared
@ -777,7 +776,6 @@ enable_sanity_checks
enable_check_abi
enable_shared
enable_profile
enable_omitfp
enable_bounded
enable_versioning
enable_oldest_abi
@ -1427,7 +1425,6 @@ Optional Features:
[default=no]
--enable-shared build shared library [default=yes if GNU ld & ELF]
--enable-profile build profiled library [default=no]
--enable-omitfp build undebuggable optimized library [default=no]
--enable-bounded build with runtime bounds checking [default=no]
--disable-versioning do not include versioning information in the library
objects [default=yes if supported]
@ -3607,13 +3604,6 @@ else
profile=no
fi
# Check whether --enable-omitfp was given.
if test "${enable_omitfp+set}" = set; then :
enableval=$enable_omitfp; omitfp=$enableval
else
omitfp=no
fi
# Check whether --enable-bounded was given.
if test "${enable_bounded+set}" = set; then :
enableval=$enable_bounded; bounded=$enableval
@ -7984,7 +7974,6 @@ $as_echo "$libc_cv_pic_default" >&6; }
if test "`(cd $srcdir; pwd)`" = "`pwd`"; then
config_makefile=
else

View File

@ -142,11 +142,6 @@ AC_ARG_ENABLE([profile],
[build profiled library @<:@default=no@:>@]),
[profile=$enableval],
[profile=no])
AC_ARG_ENABLE([omitfp],
AC_HELP_STRING([--enable-omitfp],
[build undebuggable optimized library @<:@default=no@:>@]),
[omitfp=$enableval],
[omitfp=no])
AC_ARG_ENABLE([bounded],
AC_HELP_STRING([--enable-bounded],
[build with runtime bounds checking @<:@default=no@:>@]),
@ -2367,7 +2362,6 @@ rm -f conftest.*])
AC_SUBST(libc_cv_pic_default)
AC_SUBST(profile)
AC_SUBST(omitfp)
AC_SUBST(bounded)
AC_SUBST(static_nss)
AC_SUBST(nopic_initfini)

View File

@ -136,13 +136,6 @@ linker.
Don't build libraries with profiling information. You may want to use
this option if you don't plan to do profiling.
@item --enable-omitfp
Use maximum optimization for the normal (static and shared)
libraries, and compile separate static libraries with debugging
information and no optimization. We recommend not doing this. The extra
optimization doesn't gain you much, it may provoke compiler bugs, and you
won't be able to trace bugs through the C library.
@item --disable-versioning
Don't compile the shared libraries with symbol version information.
Doing this will make the resulting library incompatible with old