public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@codesourcery.com> To: gdr@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/6090: Problem with copy of std_valarray Date: Mon, 08 Apr 2002 04:16:00 -0000 [thread overview] Message-ID: <20020408111606.4120.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/6090; it has been noted by GNATS. From: Gabriel Dos Reis <gdr@codesourcery.com> To: bkoz@gcc.gnu.org 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: 08 Apr 2002 13:06:42 +0200 bkoz@gcc.gnu.org writes: | Synopsis: Problem with copy of std_valarray | | State-Changed-From-To: feedback->analyzed | State-Changed-By: bkoz | State-Changed-When: Wed Apr 3 12:45:33 2002 | State-Changed-Why: | This looks like it is still an issue in gcc-3.1. | | include/std/std_valarray.h: 342 | | template<typename _Tp> | inline valarray<_Tp>& | valarray<_Tp>::operator= (const valarray<_Tp>& __v) | { | __valarray_copy(__v._M_data, _M_size, _M_data); | return *this; | } | | include/std/std_valarray.h: 284 | template<typename _Tp> | inline valarray<_Tp>::valarray (const valarray<_Tp>& __v) | : _M_size(__v._M_size), _M_data(__valarray_get_storage<_Tp>(__v._M_size)) | { __valarray_copy_construct (__v._M_data, __v._M_data + _M_size, _M_data); } I'm not sure I understand what the problem is about. Is the submitter complaining that copying a valarray wasn't adjusting the target's size? That is the mandated behaviour, in particular if the source and the target don't have the same length then the behaviour is undefined. -- Gaby
next reply other threads:[~2002-04-08 11:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-08 4:16 Gabriel Dos Reis [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-03 13:44 gdr 2002-04-11 16:56 Gabriel Dos Reis 2002-04-10 10:26 Benjamin Kosnik 2002-04-03 12:45 bkoz 2002-04-01 18:51 bkoz 2002-03-29 12:11 paolo 2002-03-29 2:16 erwan.goasdoue
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020408111606.4120.qmail@sources.redhat.com \ --to=gdr@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=gdr@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).