From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6426 invoked by alias); 10 Apr 2002 17:26: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 6388 invoked by uid 71); 10 Apr 2002 17:26:01 -0000 Date: Wed, 10 Apr 2002 10:26:00 -0000 Message-ID: <20020410172601.6382.qmail@sources.redhat.com> To: gdr@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Benjamin Kosnik Subject: Re: libstdc++/6090: Problem with copy of std_valarray Reply-To: Benjamin Kosnik X-SW-Source: 2002-04/txt/msg00588.txt.bz2 List-Id: The following reply was made to PR libstdc++/6090; it has been noted by GNATS. From: Benjamin Kosnik To: Gabriel Dos Reis Cc: erwan.goasdoue@ipsis.fr, gcc-bugs@gcc.gnu.org, gdr@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/6090: Problem with copy of std_valarray Date: Wed, 10 Apr 2002 09:49:17 -0700 (PDT) > That is the mandated behaviour, in particular if the source and the > target don't have the same length then the behaviour is undefined. I think the problem is that the assignment and copy ctor do different things. Why is that? -benjamin