Re: libstdc++/10064: crash when using valarray's operator=

[Gabriel Dos Reis <gdr@integrable-solutions.net>]

The following reply was made to PR libstdc++/10064; it has been noted by GNATS.

From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: brian.r.landy@wellsfargo.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/10064: crash when using valarray's operator=
Date: 14 Mar 2003 14:37:11 +0100

 brian.r.landy@wellsfargo.com writes:
 
 | >Number:         10064
 | >Category:       libstdc++
 | >Synopsis:       crash when using valarray's operator=
 | >Confidential:   no
 | >Severity:       serious
 | >Priority:       medium
 | >Responsible:    unassigned
 | >State:          open
 | >Class:          sw-bug
 | >Submitter-Id:   net
 | >Arrival-Date:   Thu Mar 13 19:56:01 UTC 2003
 | >Closed-Date:
 | >Last-Modified:
 | >Originator:     Brian Landy
 | >Release:        gcc version 3.2
 | >Organization:
 | >Environment:
 | AIX 4.3, cygwin, ...
 | >Description:
 | There is a bug in the dfinition of:
 | 
 |    valarray<_Tp>::operator= (const valarray<_Tp>& __v)
 | 
 | The target valarray is not resized to match the size of the source
 | valarray before copying.  
 
 This is not a bug.  
 
 It is an undefined behaviour if both operands of operator= doe not
 have the ame size.
 
 -- Gaby