--- Comment #13 from paolo dot carlini at oracle dot com 2009-03-13 14:58
---
I see, thanks a lot for your help. The most important point I was missing is
the use of add_reference in shared_ptr...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39405
--- Comment #12 from d dot frey at gmx dot de 2009-03-13 14:53 ---
(In reply to comment #11)
> I understand. Too bad that we can't make it to work for 4.3.x without
> regressing on libstdc++/35637 :( I'm puzzled by the fact that the tr1 version
> works, only is_reference is really differ
--- Comment #11 from paolo dot carlini at oracle dot com 2009-03-13 13:22
---
(In reply to comment #10)
> OK, I see. So maybe not worth the effort to fix in 4.3.x as long as 4.4.0 is
> fine. To make sure, could you (Paolo) please add a testcase for this to the
> testsuite for 4.4.0/trun
--- Comment #10 from d dot frey at gmx dot de 2009-03-13 13:14 ---
(In reply to comment #8)
> Moreover, if we ""fix"" this issue at the library level without dealing with
> the real C++ front-end issue, we regress on libstdc++/35637, of course.
OK, I see. So maybe not worth the effort t
--- Comment #9 from paolo dot carlini at oracle dot com 2009-03-13 13:13
---
(In reply to comment #7)
> It is a library change in the sense that it triggers a bug in the c++
> front-end. Because of course the library afterwards remained the same and the
> problem is not there anymore...
--- Comment #8 from paolo dot carlini at oracle dot com 2009-03-13 13:02
---
Moreover, if we ""fix"" this issue at the library level without dealing with
the real C++ front-end issue, we regress on libstdc++/35637, of course.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39405
--- Comment #7 from paolo dot carlini at oracle dot com 2009-03-13 13:00
---
It is a library change in the sense that it triggers a bug in the c++
front-end. Because of course the library afterwards remained the same and the
problem is not there anymore... We'll see, in case of a 4.3.4
--- Comment #6 from d dot frey at gmx dot de 2009-03-13 12:49 ---
(In reply to comment #5)
More information on this:
> > > The bug is in both 4.3.3 and 4.3.2, however it isn't in 4.3.0 on a
> > > sparcv9-sun-solaris2.10 box with 64bits. Haven't got any 4.3.1 to try.
I've copied to hea
--- Comment #5 from d dot frey at gmx dot de 2009-03-13 12:23 ---
(In reply to comment #4)
> > The bug is in both 4.3.3 and 4.3.2, however it isn't in 4.3.0 on a
> > sparcv9-sun-solaris2.10 box with 64bits. Haven't got any 4.3.1 to try.
>
> Ok. I went through the change which went in *t
--- Comment #4 from paolo dot carlini at oracle dot com 2009-03-13 09:43
---
(In reply to comment #3)
> The bug is in both 4.3.3 and 4.3.2, however it isn't in 4.3.0 on a
> sparcv9-sun-solaris2.10 box with 64bits. Haven't got any 4.3.1 to try.
Ok. I went through the change which went i
--- Comment #3 from gcc at cohi dot at 2009-03-13 07:33 ---
The bug is in both 4.3.3 and 4.3.2, however it isn't in 4.3.0 on a
sparcv9-sun-solaris2.10 box with 64bits. Haven't got any 4.3.1 to try.
If 4.4.0 is out before 4.3.4 (if there is such a thing), it might not really
not be worth
--- Comment #2 from paolo dot carlini at oracle dot com 2009-03-12 20:01
---
Indeed, mainline is fine. Do we have evidence that some earlier 4.3.x release
worked? Because, otherwise, given that 4.3.x is approaching is end of life in
terms of expected releases, this issue can be safely c
--- Comment #1 from gcc at cohi dot at 2009-03-12 17:00 ---
Just now I installed pre-release gcc-4.4-20090306 and there is no error with
t.cc as shown, so it seems to be a bug that has been already fixed; I didn't
check any 4.3.4 pre-release however.
--
http://gcc.gnu.org/bugzilla/s
13 matches
Mail list logo
