From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13818 invoked by alias); 14 Mar 2003 15:46:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 13725 invoked by uid 71); 14 Mar 2003 15:46:01 -0000 Date: Fri, 14 Mar 2003 15:46:00 -0000 Message-ID: <20030314154601.13714.qmail@sources.redhat.com> To: gdr@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Gabriel Dos Reis Subject: Re: libstdc++/10064: crash when using valarray's operator= Reply-To: Gabriel Dos Reis X-SW-Source: 2003-03/txt/msg00867.txt.bz2 List-Id: The following reply was made to PR libstdc++/10064; it has been noted by GNATS. From: Gabriel Dos Reis To: Brian.R.Landy@mortgage.wellsFargo.COM Cc: libstdc++@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/10064: crash when using valarray's operator= Date: 14 Mar 2003 16:33:30 +0100 Brian.R.Landy@mortgage.wellsFargo.COM writes: | Sorry, I assumed it should resize since MS's STL (in VC++ 6.0) does resize. | I take it this is particular to valarray? Yes, the behaviour I was describing is particular to valarray<> -- as opposed to vector<> which does resizing. Valarray<> should be thought of as a low level building bloc. Automatic resizing is too high level for the purpose of valarray. | Because I think I remember | checking vector (in gcc's STL) and it does. By undefined do you mean that | the behavior is left up to the implementer, or that MS should not do the | resize? Thanks! By "undefined behaviour", I meant what the C++ standard means. Anything can happen. The implementation may accept or reject it, or the program may reformat your hard drive. Thanks, -- Gaby