--- Comment #15 from gdr at integrable-solutions dot net 2010-02-06 22:21
---
Subject: Re: valarray uses __cos which may conflict with
libm functions
On Sat, Feb 6, 2010 at 2:44 PM, paolo dot carlini at oracle dot com
wrote:
> --- Comment #14 from paolo dot carlini at or
--- Comment #14 from paolo dot carlini at oracle dot com 2010-02-06 20:44
---
Done.
--
paolo dot carlini at oracle dot com changed:
What|Removed |Added
Statu
--- Comment #13 from paolo at gcc dot gnu dot org 2010-02-06 20:41 ---
Subject: Bug 27340
Author: paolo
Date: Sat Feb 6 20:41:09 2010
New Revision: 156555
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=156555
Log:
2010-02-06 Paolo Carlini
PR libstdc++/27340
--
paolo dot carlini at oracle dot com changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |paolo dot carlini at oracle
|dot org
--- Comment #12 from paolo dot carlini at oracle dot com 2010-02-06 19:42
---
I totally agree. Anyway, ok, I can do that, it will require a bit of tweaking
to the valarray_after.h macros, no big deal.
--
paolo dot carlini at oracle dot com changed:
What|Removed
--- Comment #11 from gdr at gcc dot gnu dot org 2010-02-06 19:17 ---
(In reply to comment #10)
> I'll re-open this only if Gaby, maintainer of valarray, thinks it's the right
> thing to do.
>
If someone wants to rename __cos to _Cos, that is fine by me.
But, it should be noted that thi
--- Comment #10 from paolo dot carlini at oracle dot com 2010-02-06 19:07
---
I'll re-open this only if Gaby, maintainer of valarray, thinks it's the right
thing to do.
--
paolo dot carlini at oracle dot com changed:
What|Removed |Added
--
--- Comment #9 from marc dot glisse at normalesup dot org 2010-02-06 17:52
---
(In reply to comment #8)
> It seems this can be safely closed as invalid, there is no reason why
> std::__cos should be wrong.
Marking this as invalid means that we can never include solaris libc headers
wit
--- Comment #8 from paolo dot carlini at oracle dot com 2010-02-05 13:07
---
It seems this can be safely closed as invalid, there is no reason why
std::__cos should be wrong.
--
paolo dot carlini at oracle dot com changed:
What|Removed |Added
--- Comment #7 from gdr at integrable-solutions dot net 2006-05-01 23:39
---
Subject: Re: valarray uses __cos which may conflict with libm functions
"marc dot glisse at normalesup dot org" <[EMAIL PROTECTED]> writes:
| (In reply to comment #4)
| > Should all those private classes and
--- Comment #6 from marc dot glisse at normalesup dot org 2006-04-28 21:57
---
(In reply to comment #4)
> Should all those private classes and functions be declared in some
> specific namespace std::glibcxx_private to have a single point of failure?
Oups, I just noticed that was one o
--- Comment #5 from pcarlini at suse dot de 2006-04-28 21:18 ---
(In reply to comment #4)
> Convinced of what?
Of course convinced that before renaming and re-renaming (endlessly, in
principle) we should really give some serious tought to those issues, figure
out what we are trying to
--- Comment #4 from marc dot glisse at normalesup dot org 2006-04-28 20:43
---
(In reply to comment #3)
> Well, I think Andrew has a point: suppose we rename all those functions to
> _M_cos and co. Then, later, we discover that a third libc (not Solaris, not
> GNU) conflicts with those
--- Comment #3 from pcarlini at suse dot de 2006-04-28 20:01 ---
(In reply to comment #2)
> (In reply to comment #1)
> > Both libc and libstdc++ are considered part of the implementation which
> > means
> > both are valid to use this name space.
>
> Which means both should take care no
--- Comment #2 from marc dot glisse at normalesup dot org 2006-04-28 10:33
---
(In reply to comment #1)
> Both libc and libstdc++ are considered part of the implementation which means
> both are valid to use this name space.
Which means both should take care not to use a name (in this
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-04-27 19:07 ---
Both libc and libstdc++ are considered part of the implementation which means
both are valid to use this name space.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27340
16 matches
Mail list logo
