This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.18 freeze!
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: libc-alpha at sourceware dot org, Adhemerval Zanella <azanella at linux dot vnet dot ibm dot com>
- Date: Wed, 12 Jun 2013 16:15:14 -0400
- 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> <51B893F9 dot 6010401 at linux dot vnet dot ibm dot com> <20130612184717 dot GA179 at winnix>
On 06/12/2013 02:47 PM, Winfried Magerl wrote:
> gcc-4.8.1 is already released and even with a future gcc-fix (if bug is
> accpeted) it might be necessary to add some workaround for this problem
> befor releasing glibc-2.18.
Adhemerval,
Given your familiarity with the issue do you have time to fix the
memset issue in glibc so that we can compile with the already released
gcc-4.8.1?
One solution could be a configure check that detects the transformation
is present, sets a flag, and then disables the transformation when building
the appropriate file.
The best example I can give is a recent fix I did for detecting when
__sync_val_compare_and_swap is used e.g. commit
a01f19c8fb12eef419d4112879bc715e2ab6f6d7
You can use a variable to set something in config.make, which then
gets used to decided to enable or disable the feature.
Cheers,
Carlos.