From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) by sourceware.org (Postfix) with ESMTPS id BCDF438618EB for ; Wed, 5 Aug 2020 16:54:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org BCDF438618EB Received: by mail-ej1-x629.google.com with SMTP id o23so19718865ejr.1 for ; Wed, 05 Aug 2020 09:54:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:cc:from :message-id; bh=dhMJgjCglHvE+t2N7aZF4GcGV2SYzNwAeErKX1jxPyM=; b=F01aqz/0whkwkyBkERiK67vHDVswQCOvVuxx7nNrJ6L+jsLIO/v/Foige7Bju1D8Sq +0u2QLOI4LyCjYkZq+TGb1fwi/i5OhspSYISzq//wPsuUlkvrM5/I0SQ1KeGOEE+Iknd sFwyMdlz49HeKsY94emuWGnTeO6pjsoLieMzGzXx6+mCkV1raOl6yrctYrDR3ea4DySE GKpcNAbCqgGcd3/9MxCpseQFipNSq62kX5I9DlW+Eeh85xlnEZJhi7rYlsvziFVnOvwK /7vLs9ZmXYJQ6YG5NBEapPzZi3beMEztwZShp0BrxfQhE+P4iM7TBGtG8NuTadgW6ysc /Vuw== X-Gm-Message-State: AOAM530dRYuuSciwn6hdx909Y4STVuQQwaqkPhOegmEEEDQixamxlwmS gTGuzdksp5EQtMd7ZsgZ6RJ3SAtP X-Google-Smtp-Source: ABdhPJxGI7YlpN8+BfWVOkBlRiKHv5gBasJkk+oQ0Xdjwz/OGF5o5RJoMG2mTR9jk1KQ62WS+Tb5zQ== X-Received: by 2002:a17:906:6408:: with SMTP id d8mr137618ejm.345.1596646451740; Wed, 05 Aug 2020 09:54:11 -0700 (PDT) Received: from [192.168.178.32] (x5f72533a.dyn.telefonica.de. [95.114.83.58]) by smtp.gmail.com with ESMTPSA id by3sm1899024ejb.9.2020.08.05.09.54.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Aug 2020 09:54:11 -0700 (PDT) Date: Wed, 05 Aug 2020 18:54:08 +0200 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: std:vec for classes with constructor? (Was: Re: [patch] multi-range implementation for value_range (irange)) To: gcc-patches@gcc.gnu.org, Martin Jambor , Aldy Hernandez , Jeff Law CC: gcc-patches From: Richard Biener Message-ID: <5EE6522C-086B-42E0-B42A-F291E09C422A@gmail.com> X-Spam-Status: No, score=-3.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2020 16:54:14 -0000 On August 5, 2020 5:09:19 PM GMT+02:00, Martin Jambor w= rote: >On Fri, Jul 31 2020, Aldy Hernandez via Gcc-patches wrote: >> > >[=2E=2E=2E] > >> >> * ipa-cp changes from vec to std::vec=2E >> >> We are using std::vec to ensure constructors are run, which they >aren't=20 >> in our internal vec<> implementation=2E Although we usually steer away > >> from using std::vec because of interactions with our GC system,=20 >> ipcp_param_lattices is only live within the pass and allocated with >calloc=2E >> > >Ummm=2E=2E=2E I did not object but I will save the URL of this message in= the >archive so that I can waive it in front of anyone complaining why I >don't use our internal vec's in IPA data structures=2E > >But it actually raises a broader question: was this supposed to be an >exception, allowed only not to complicate the irange patch further, or >will this be generally accepted thing to do when someone wants to have >a >vector of constructed items? It's definitely not what we want=2E You have to find another solution to t= his problem=2E=20 Richard=2E=20 >Thanks, > >Martin