--- Comment #6 from paolo dot carlini at oracle dot com 2009-12-27 14:41
---
Thus you mean only 40134 is involved. Because 40133 *assumes* that on the
relevant linux targets there are no surprises with shared vs static libgcc.
In general, I want to make sure nothing changes in the com
--- Comment #5 from mikpe at it dot uu dot se 2009-12-27 13:59 ---
(In reply to comment #4)
> Note, however, that something is definitely wrong in the analysis: PR40133 and
> PR40134 have been fixed **only in mainline**, thus per se those changes cannot
> be involved in a breakage involv
--- Comment #4 from paolo dot carlini at oracle dot com 2009-12-27 12:18
---
Note, however, that something is definitely wrong in the analysis: PR40133 and
PR40134 have been fixed **only in mainline**, thus per se those changes cannot
be involved in a breakage involving 4_4-branch. As f
--- Comment #3 from paolo dot carlini at oracle dot com 2009-12-27 11:59
---
Yes, unless Matthias has a good explanation and fix for what's going on, those
changes should be immediately reverted, I will do that anyway in 3-4 days max.
--
paolo dot carlini at oracle dot com changed:
--- Comment #2 from ramana at gcc dot gnu dot org 2009-12-27 11:37 ---
The correct fix is potentially a version of the fix for PR40133 / PR40134 for
arm-linux-gnueabi. Looking at this.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42503
--- Comment #1 from mikpe at it dot uu dot se 2009-12-26 14:59 ---
Reverting r155171 allows gcc-4.4-20091215 to build a working libjava again.
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=155171
Log:
2009-12-11 Ramana Radhakrishnan
PR target/42263
2009-08-11
