On 30-Oct-11, at 8:21 PM, Carlos O'Donell wrote:
On Sun, Oct 30, 2011 at 12:13 PM, John David Anglin
<dave.anglin@xxxxxxxx> wrote:
On 30-Oct-11, at 11:31 AM, Rolf Eike Beer wrote:
John David Anglin wrote:
This problem is fixed in the GCC trunk and 4.4, 4.5 and 4.6
branches.
libmpfr4-3.1.0 now passes all tests.
Can we get a link to a bug or a commit so we could easily put this
into
the
gentoo patchset for local usage until a new version is released?
The trunk patch is on the gcc-patches list:
http://gcc.gnu.org/ml/gcc-patches/2011-10/msg02758.html
There are two variants of the patch:
http://gcc.gnu.org/viewcvs?view=revision&revision=180655
http://gcc.gnu.org/viewcvs?view=revision&revision=180662
The first is for 4.7. The latter applies to 4.4, 4.5 and 4.6.
Awesome! Great work Dave! :-)
Thanks, but this fix wasn't that hard... I had a little trouble with
the testing
due to other issues. Many GCC bugs are much harder. Things are easy
when the compilation bug is clear.
I integrated Guy's patch into debian 2.13-10 today and I was going to do
a build, but then I discovered it builds using 4.4. So, I patched 4.4
with the
above change, and will rebuild 2.13 when it's done. Hopefully, this
will
fix the udev bug which is blocking many python builds. I'm interested
to
see if the glibc testsuite results will be better.
It's a bit unclear how extensively TLS variables are used, but maybe
fixing
this will make it easier to resolve the remaining pthread bugs.
I've been wondering how much is left to install to glibc head?
Dave
--
John David Anglin dave.anglin@xxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
