--- Comment #10 from rguenth at gcc dot gnu dot org 2009-05-11 12:23
---
Did I say fixed?
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
Stat
--- Comment #9 from rguenth at gcc dot gnu dot org 2009-05-11 12:23 ---
Ok, I simply consider this fixed for 4.5.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #8 from rguenth at gcc dot gnu dot org 2009-05-10 16:41 ---
Subject: Bug 40081
Author: rguenth
Date: Sun May 10 16:40:55 2009
New Revision: 147349
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=147349
Log:
2009-05-10 Richard Guenther
PR tree-optimization/
--- Comment #7 from jamborm at gcc dot gnu dot org 2009-05-10 10:29 ---
New SRA handles this fine by not scalarizing anything that has volatile fields
in it. There is already a fortran testcase with a union with a volatile field
that made me aware of this.
--
http://gcc.gnu.org/bugz
--- Comment #6 from rguenth at gcc dot gnu dot org 2009-05-10 10:16 ---
Subject: Bug 40081
Author: rguenth
Date: Sun May 10 10:16:01 2009
New Revision: 147330
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=147330
Log:
2009-05-10 Richard Guenther
PR tree-optimization/
--- Comment #5 from rguenth at gcc dot gnu dot org 2009-05-09 18:07 ---
Mine.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned
--- Comment #4 from rguenth at gcc dot gnu dot org 2009-05-09 17:57 ---
Same problem in 4.4, 4.3 and 4.2, just only the type verifier verifies this.
It's not critial (it will be treated the same as struct copies - thus it is
simply inefficient). I'll see if a fix is simple.
--
rguen
--- Comment #3 from rguenth at gcc dot gnu dot org 2009-05-09 13:34 ---
struct Atomic_t {
Atomic_t(int i) : val(i) { }
volatile int val;
};
class RefCount {
public:
RefCount(Atomic_t c) : m_count(c) { }
Atomic_t m_count;
};
class IntrusiveCountableBase {
RefCount m_u
