From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id EC9F03858D20 for ; Tue, 8 Aug 2023 15:21:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org EC9F03858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=polymtl.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=polymtl.ca Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 378FLLa9002078 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 8 Aug 2023 11:21:25 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 378FLLa9002078 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=polymtl.ca; s=default; t=1691508086; bh=17oxTPbCSNmC3pDoeeJ9OF1bcre8Uaz9h44imkvJe2g=; h=Date:From:To:CC:Subject:In-Reply-To:References:From; b=W0U1KANwJABXbvDy50lMWU/hyqYycIguwF8M+bLFl1Ah7moBcKTLtcRRv23ihN9nh 5uHq0TolqJPmDPTLJnOUrIt96Z3HFYs/ICq5j/UMaC0uurtELxEjiyxkyiKtGIYB0g crN03BzCtYmDNf3Pub0MWkLPIsM2ylml4S/1ssKM= Received: from [127.0.0.1] (unknown [204.48.95.123]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 79F341E028; Tue, 8 Aug 2023 11:21:20 -0400 (EDT) Date: Tue, 08 Aug 2023 11:21:18 -0400 From: Simon Marchi To: Tom Tromey CC: Tom de Vries , Tom de Vries via Gdb-patches Subject: Re: [PATCH] [gdb/build] Fix build breaker with -std=c++11 User-Agent: K-9 Mail for Android In-Reply-To: <87r0oe7b2k.fsf@tromey.com> References: <20230806235915.18746-1-tdevries@suse.de> <51561E9D-24F0-48CB-A563-50F29C2966D9@polymtl.ca> <87r0oe7b2k.fsf@tromey.com> Message-ID: <1E8AD5B8-C0AF-4756-838A-ECE3D0FAFC01@polymtl.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Tue, 8 Aug 2023 15:21:21 +0000 X-Spam-Status: No, score=-3030.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On August 7, 2023 6:16:19 p=2Em=2E EDT, Tom Tromey wrot= e: >Simon> When we encounter things like this, should we add some greppable >Simon> TODO comment to record an actionable item for when we switch to a >Simon> more recent C++ version? > >FWIW I know of one other instance of this, in gdb_demangle: > > std::string copy =3D name; > run_on_main_thread ([=3D] () > { > report_failed_demangle (copy=2Ec_str (), core_dump_allowed, > >Here, the name is copied twice, but with move captures there could be >just a single copy=2E > >I wonder when we can switch to C++14=2E If I recall, Tom de Vries said they have to support some SLES version that= has gcc 4=2Ex as the system compiler for a while still=2E Other than that= I am not aware of anything holding back=2E=20 Simon=20