This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: libsanitizer merge from upstream r196090
- From: Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>
- To: Jeff Law <law at redhat dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, Uros Bizjak <ubizjak at gmail dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, "H.J. Lu" <hjl dot tools at gmail dot com>, Dodji Seketeli <dodji at redhat dot com>, Marek Polacek <polacek at redhat dot com>, Dmitry Vyukov <dvyukov at google dot com>, Evgeniy Stepanov <eugenis at google dot com>, Alexey Samsonov <samsonov at google dot com>
- Date: Wed, 4 Dec 2013 05:52:11 +0100
- Subject: Re: libsanitizer merge from upstream r196090
- Authentication-results: sourceware.org; auth=none
- References: <CAFULd4ZrFy-o7GmDh31WRpoxiYwwLpaAY6pOtxCZ9i-+4kfv1A at mail dot gmail dot com> <CAGQ9bdzMRvFOWXmAbRoXAM4otn6JMR8AALspJ1s=hP=jgm7KXQ at mail dot gmail dot com> <CAFULd4Z-HrnYedyH_fcH1knQAD+=4jmC_xOBacgs2-DJhGWD0Q at mail dot gmail dot com> <CAGQ9bdz4Qm8nGJhLPJ9wwP71rUC4CddaReqWsbUqLq-GZSqRTA at mail dot gmail dot com> <20131203114959 dot GW892 at tucnak dot redhat dot com> <CAGQ9bdwvEB7-TGoycetGmMOqs6Xe=uW0bVn8KAWMooaSYe6nUQ at mail dot gmail dot com> <20131203154709 dot GA892 at tucnak dot redhat dot com> <529E09FB dot 30901 at redhat dot com>
>>>
>>> This won't happen any time soon, right?
>>> I'd like to ask glibc for many other things, not just this, but the
>>> latency
>>> of the glibc changes propagating to users is too low, so we don't
>>> bother (although we should)
>>> E.g. we've been hit by the ugly
>>> pthread_getattr_np/pthread_attr_getstack multiple times.
>>> :(
>>
>>
>> If you never ask for it, it will never be done, it is that simple.
>
> glibc pushes out a release every six months which then gets put into the
> next Fedora release which usually follows a few months later. We're talking
> about a worst case lag time of roughly 9 months, often much less. It's
> probably similar for the SuSE community releases.
>
> I think everyone who has had a bad experience working with glibc's team in
> the past should try to put it behind them. The new team running glibc is
> much more reasonable to work with -- the biggest problem now is rebooting
> the project after years of mis-management. The progress they've made
> towards that over the last year has been tremendous.
>
Submitted a feature request against glibc
https://sourceware.org/bugzilla/show_bug.cgi?id=16291
Please comment there if you think I did not provide enough information.
--kcc