This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

first test release for glibc 2.2.3

I've uploaded to

the files

  glibc-2.2.3pre1.tar.bz2                     (also .gz)
  glibc-2.2.2-2.2.3pre1.diff.bz2              (also .gz)
  glibc-linuxthreads-2.2.3pre1.tar.bz2        (also .gz)

which contain the first test release for glibc 2.2.3.  This is not a
pure bugfix release.  It contains a number of improvements and new

Version 2.2.3

* Intel's IA-64 math library is largely integrated.  It provides fast and
  accurate implementatations for most basic and standard math functions
  in float, double, and long double format.

* Stephen Moshier implemented j0, j1, jn, y0, y1, yn, lgamma, erf, and
  erfc for the 96-bit long double format.

* The beginning of a last-bit accurate math library by IBM Haifa were added.
  The basic double functions exist today.  Contributed by Abraham Ziv
  <>, Moshe Olshansky <>, Ealan Henis
  <>, and Anna Reitman <>.

* An asynchronous name lookup library was added.  The interface is designed
  after POSIX AIO.  The proposal was circulated beforehand to get comments.
  No negative ones came in.  Implemented by Ulrich Drepper.

* Port to S390/64bit contributed by Martin Schwidefsky

* David Mosberger <> implemented the setcontext family
  of functions for Linux/IA-64.

* The RPC code is now thread safe.  Threads can now use the same service
  of different services at the same time.  Patch by Eric Norum
  <> with some help by Ulrich Drepper.

The asynchronous name lookup code is not yet documented in the manual
but my original whitepaper is available at

One other change is noting worthwhile.  To implement atexit() in the
present of dlopen() according to the upcoming Unix standard the
definition of atexit() is changed in a way which can cause problems
with most of today's gccs.  The problem is some code in gcc which was
necessary in libc5 but not with glibc.  A patch for gcc is available

For a description of the problem look at

One final bit, the RPC code is now thread-safe but this didn't come
without a price.  Due to the "clever" (NOT!) design of the interface
it is not possible to transparently replace the use of the global
variable rpc_createerr with a hidden function call which does the
right thing.  The reason is that there is a data type with the same
name.  Very clever, Sun!  There are two possibilities implemented:

- use get_rpc_createerr() to the variable reference

- define _RPC_MT_VARS before including the RPC headers.  This will
  define a macro rpc_createerr which can cause the problem described

As usual, report success and failures to  According to the reports for
previous release there are less than 10 people actually trying the
test releases since I never get feedback from more than 10 people.
Consider reporting also success since this is the only indicator I
have that no problems exist.

---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at   `------------------------

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]