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]

Re: Update on freeze status of glibc 2.18?


On Fri, 2013-06-21 at 00:24 +0200, Andi Kleen wrote:
> > And it will not disallow elision for these cases.  As Roland points out,
> 
> It would for existing binaries.

That's not the concern you raised initially.  So, can we conclude that
for the subset of newly compiled binaries, you wouldn't have concerns
anymore about the DEFAULT != NORMAL split approach?

> I really don't want to recompile
> everything. I don't think people recompile their binaries all
> the time.

If this is just about *you*, then I think it's better to not break POSIX
requirements even if you have to recompile stuff.

If you were talking about potential users, then which scenarios do you
have in mind?  If people use the stock glibc that their distribution
provides, then the applications provided by the distribution will also
have been recompiled.  That already gives you a large group of users and
applications, and good testing.  If you're thinking third-party
binaries, then they'll have to be recompiled to make use of new features
-- but that's hardly unusual.




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