This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.18 freeze!
- From: Adhemerval Zanella <azanella at linux dot vnet dot ibm dot com>
- To: libc-alpha at sourceware dot org
- Date: Wed, 12 Jun 2013 12:30:01 -0300
- Subject: Re: glibc 2.18 freeze!
- References: <51ACFE36 dot 5000603 at redhat dot com> <CAAKybw9ZuOKSpXgCGb5mFVHkKmrnUCKAdStg+i7+_ckUM9Qp2g at mail dot gmail dot com> <51ADFC0B dot 1060907 at linux dot vnet dot ibm dot com> <20130611183029 dot B62D52C0A2 at topped-with-meat dot com> <51B78382 dot 6000403 at linux dot vnet dot ibm dot com> <20130611213211 dot EA4E12C09F at topped-with-meat dot com>
On 11-06-2013 18:32, Roland McGrath wrote:
>> I opened http://sourceware.org/bugzilla/show_bug.cgi?id=15605 to track it
>> and updated patch is below. My patch however only fixes the
>> check-localplt issue I observed in PPC32/PPC64 builds with GCC 4.8 +
>> O3. The issue reported at
>> <http://sourceware.org/ml/libc-alpha/2013-05/msg00730.html>http://sourceware.org/ml/libc-alpha/2013-05/msg00730.html
>> needs another solution.
> Thanks. This looks fine for now.
>
> Who is going to take responsibility for filing a GCC bug about the broader
> issue, following up now with related workarounds we might need for 4.8, and
> following up in the future to replace workarounds with proper solutions
> when GCC makes them available?
>
>
> Thanks,
> Roland
>
Pushed as 6a97b62a5b4f18aea849d6f4d8de58d1469d2521. I'll fill a GCC bug
about this issue. I can think some possible solutions:
* Add a option like -f tree-loop-distribute-patterns-prepend=XXX where GLIBC
can add "__GI_";
* Add a algorithm to check if symbol's name is memset/memove and then
not generate the recursive call.
Any other possible solution to add on the bug report?