[Bug target/42503] gcc-4.4-20091215 broke libjava on ARM
--- 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
[Bug target/42503] gcc-4.4-20091215 broke libjava on ARM
--- 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: What|Removed |Added CC||doko at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42503
[Bug target/42503] gcc-4.4-20091215 broke libjava on ARM
--- 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 far as libstdc++ is concerned, in particular, in 4_4-branch we are not trying to do link-test anywhere, we cannot make mistakes about static libgcc symbols. Still, I'm seeing something puzzling and alarming here from the point of view of those issues and I would recommend Matthias to also have a look. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42503
[Bug target/42503] gcc-4.4-20091215 broke libjava on ARM
--- 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 involving 4_4-branch. I believe it's the *absence* of the PR40134 fix on 4_4-branch that's causing the backport of __sync_synchronize() support to regress. I'm currently testing 4.4-20091215 with relevant bits of PR40134 backported (r151568 + r152975): that cured the build failure, but the testsuite run is not yet finished. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42503
[Bug target/42503] gcc-4.4-20091215 broke libjava on ARM
--- 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 compiler-proper that breaks the assumptions of 40133, which then would have to be reverted. For now mainline seems still ok, I think Matthias tests regularly those targets. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42503
[Bug target/42503] gcc-4.4-20091215 broke libjava on ARM
--- 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=gccview=revrev=155171 Log: 2009-12-11 Ramana Radhakrishnan ramana.radhakrish...@arm.com PR target/42263 2009-08-11 Andrew Haley a...@redhat.com * config/arm/arm.c (arm_init_libfuncs): Add __sync_synchronize. I suspect ARM's static libgcc has more symbols than the shared one bug is involved here (see PR40133 and PR40134). -- mikpe at it dot uu dot se changed: What|Removed |Added CC||ramana dot radhakrishnan at ||arm dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42503
