This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/3247: valarray private member
- To: bkoz at gcc dot gnu dot org
- Subject: Re: libstdc++/3247: valarray private member
- From: Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>
- Date: 27 Jun 2001 10:06:25 +0200
- Cc: bkoz at gnu dot org, gcc-bugs at gcc dot gnu dot org, gdr at gcc dot gnu dot org
- Organization: CMLA, ENS Cachan -- CNRS UMR 8536 (France)
- References: <20010627001418.20055.qmail@sourceware.cygnus.com>
bkoz@gcc.gnu.org writes:
| Synopsis: valarray private member
|
| Responsible-Changed-From-To: unassigned->gdr
| Responsible-Changed-By: bkoz
| Responsible-Changed-When: Tue Jun 26 17:14:18 2001
| Responsible-Changed-Why:
| Gaby I'm assigning this to you.
Thank you.
| AFAIK, this class of bugs in
| gslice_array
| mask_array
| indirect_array
I've fixed the problem for indirect_arrays. It remains to address
gslice_arrays and mask_arrays.
| represent the only valid code that I cannot compile with g++/libstdc++.
|
| Any thoughts on fixing this? I'm not quite sure what the deal is: is this a problem with the standard, or what? Other libraries don't have problems with this kind of code.
That is a problem in the Standard specification. Please have a look
at a paper of mine "Fixing valarray for real world use" (accessible
from the LWG website) and DR 253.
-- Gaby