This is the mail archive of the libc-alpha@sourceware.org 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]
Other format: [Raw text]

Request for clarification on the 128bit long double requirments


I would like to understand better why and how this GCC 4.1 requirement
for adding 128bit long double support came about.   Maybe better
understanding how this "mistake" came to happen will better understand
why GCC 4.1 will be delayed because of this change?

What I am looking for is the dicussion where glibc decided to
move over and to require GCC to move over too.  What I can
find is mails from July and March of last year for a glibc
patch and then an updated one from last month[1] which seems
to me to be the catalists for this whole mess but no replies.

So is this mess all caused by that one patch and maybe some
backroom discussing?  And from the looks of it RedHat forcing
the hand to move which seems wrong as it means that Redhat is
forcing GCC and glibc to do what they want for their distro.


Thanks,
Andrew Pinski

[1] http://sourceware.org/ml/libc-hacker/2006-01/msg00061.html


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