From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-a1p-077438.sys.comcast.net (resqmta-a1p-077438.sys.comcast.net [IPv6:2001:558:fd01:2bb4::4]) by sourceware.org (Postfix) with ESMTPS id 64EC43857720 for ; Mon, 12 Jun 2023 22:27:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 64EC43857720 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=comcast.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=comcast.net Received: from resomta-a1p-077052.sys.comcast.net ([96.103.145.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resqmta-a1p-077438.sys.comcast.net with ESMTP id 8kmfqFYWmrQWx8q05qqHHq; Mon, 12 Jun 2023 22:27:01 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1686608821; bh=2eNUFNyyb4NhwZR3LVgX4u1loaiKa859DgYIUQtYEeU=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To:Xfinity-Spam-Result; b=BIcv/Q4lyjA1giI8EL9iA4j3NmOE4tJoSzhADsKPMakRlXwtaP51ZfwYnLh1khPEd 8kZGerwAzUbgBVTl6xQw0k8yzRyAuluXkUrUQRs9hmUqmmWbxUt/Cxxk8qj0Ik3MZ+ gZMmz2uGU/AKVQvh2JhxEx1d7PKLgQ+Tvym4dfa1jg529LVOlwqxu23FI5cFh1m/Ic tQ0yKi9hFVLXwregPLlS+7xbT8+iIzZYqZei0wiozmD6sI5iSWIE+ptn58gHMJwUbu rxRS3VbXEhjqx0Tu6FXbZXzLze1wXlWZ2jwO/G26olyWUlFtz/MMoJ0qFoTZG4E3iK alRdZtyRhrUpw== Received: from smtpclient.apple ([IPv6:2601:644:907e:8d30:d35:e3d7:6832:d895]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-a1p-077052.sys.comcast.net with ESMTPSA id 8pzgqxDTH0l948pzhqwEzb; Mon, 12 Jun 2023 22:26:38 +0000 X-Xfinity-VMeta: sc=-100.00;st=legit Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: Splitting up 27_io/basic_istream/ignore/wchar_t/94749.cc (takes too long) From: Mike Stump In-Reply-To: <20230612103506.0d9842fe@nbbrfq.loc> Date: Mon, 12 Jun 2023 15:26:35 -0700 Cc: Mike Stump via Gcc-patches , Hans-Peter Nilsson , jwakely@redhat.com, Thomas Schwinge Content-Transfer-Encoding: quoted-printable Message-Id: <30721EE6-4503-44FE-B0A4-28F9F92585F0@comcast.net> References: <20230609162026.CC34320433@pchp3.se.axis.com> <7F48B21B-835B-4741-9B9E-660A2D302A67@comcast.net> <057BCABA-67C8-4309-B7DD-C9310B938727@gmail.com> <0334D52C-D33F-4261-8705-F3736D6F36B2@comcast.net> <20230612103506.0d9842fe@nbbrfq.loc> To: Bernhard Reutner-Fischer X-Mailer: Apple Mail (2.3696.120.41.1.3) X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE 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 Jun 12, 2023, at 1:35 AM, Bernhard Reutner-Fischer = wrote: >=20 > On Sat, 10 Jun 2023 11:29:36 -0700 > Mike Stump wrote: >=20 >> On Jun 9, 2023, at 2:47 PM, Bernhard Reutner-Fischer >> wrote: >=20 >>> But well. Either way, what >>> should we do about remote env, if there is one? If the target >>> supports it, send it and skip otherwise? =20 >=20 >> So, to focus a >> conversation, which target, which host, canadian? Which part of the >> environment? What part is missing you want to fix? Want to unify >> between targets... and so on. >>=20 >=20 > The most recent target where this came up again was GCN i think. > See the last block in > = https://inbox.sourceware.org/gcc-patches/20230508195217.4897009f@nbbrfq/ > and Thomas' reference therein to Tobias' > = https://inbox.sourceware.org/gcc-patches/018bcdeb-b3bb-1859-cd0b-a8a92e26d= 3a0@codesourcery.com/ >=20 > thoughts? I kinds like the remote_setenv approach, but the low level details when = one gets in there and wires up all they need to make it work are = important. If someone wants to tilt at the problem, I'm inclined to let them find = the incantation they like and approve it. I'd rather approve a patch that takes us a step closer to perfection = then go another 10 years. For quoting. I like quite using ' if there is = no ' in the string. For each ' in the string, replace it with '\'', = inelegant, but easier to reason about and don't have to worry about as = many meta characters if you try and go the "" route. This assumes something like sh is taking in commands. This isn't always = the case. One can canadian into a windows box or some other weird thing = so the mechanism used has to be next to the thing that knows what it is = talking to. Just because someone contributes code for talking to sh, doesn't mean = they have to bother with windows or other weird stuff. The next person = to come along can tilt at that.