--- Comment #16 from rguenth at gcc dot gnu dot org 2010-01-05 15:17
---
Is this fixed now?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42503
--- Comment #17 from mikpe at it dot uu dot se 2010-01-05 15:41 ---
Fixed now, closing.
--
mikpe at it dot uu dot se changed:
What|Removed |Added
Status|NEW
--- Comment #15 from doko at gcc dot gnu dot org 2010-01-04 15:13 ---
Subject: Bug 42503
Author: doko
Date: Mon Jan 4 15:13:08 2010
New Revision: 155617
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=155617
Log:
2010-01-04 Mikael Pettersson mi...@it.uu.se
PR
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|--- |4.4.3
--- Comment #11 from ramana at gcc dot gnu dot org 2009-12-29 10:24 ---
(In reply to comment #7)
(In reply to comment #5)
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
--- Comment #12 from mikpe at it dot uu dot se 2009-12-29 13:05 ---
Created an attachment (id=19413)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19413action=view)
pr40134 generic + arm bits
This is the version of the PR40134 patch I intend to submit, unless Matthias
wants to
--- Comment #13 from debian-gcc at lists dot debian dot org 2009-12-29
13:34 ---
looks fine to me (but I cannot approve). I'm using this patch already for
package builds without seeing regressions.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42503
--- Comment #14 from mikpe at it dot uu dot se 2009-12-29 23:15 ---
Patch submitted:
http://gcc.gnu.org/ml/gcc-patches/2009-12/msg01192.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42503
--- Comment #8 from doko at ubuntu dot com 2009-12-28 09:40 ---
Created an attachment (id=19399)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19399action=view)
pr40134 for 4.4
Mikael's analysis seems to be right; the __sync_synchronise backport requires
the backport of pr40134.
--- Comment #9 from paolo dot carlini at oracle dot com 2009-12-28 10:37
---
Good. To clarify, I have no personal objections to that specific kind of
backport to 4_4-branch... seems a bit late, but still, since the basic issue is
a wrong-code... up to the maintainers.
--
--- Comment #10 from mikpe at it dot uu dot se 2009-12-28 12:11 ---
Matthias, your Debian patch includes the following, which is not part of the
trunk fix for PR40134 but instead appears to be a fragment from an early
version of the PR41175/PR40677 fix (which seems to depend on
--
ramana at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last
--- Comment #7 from mikpe at it dot uu dot se 2009-12-28 00:46 ---
(In reply to comment #5)
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
13 matches
Mail list logo
