From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from elaine.keithp.com (home.keithp.com [63.227.221.253]) by sourceware.org (Postfix) with ESMTPS id 70F6A3857C7D for ; Mon, 7 Dec 2020 20:41:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 70F6A3857C7D Received: from localhost (localhost [127.0.0.1]) by elaine.keithp.com (Postfix) with ESMTP id 21A8B3F2E1F1; Mon, 7 Dec 2020 12:41:46 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at keithp.com Received: from elaine.keithp.com ([127.0.0.1]) by localhost (elaine.keithp.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id GcTqbFvPZtff; Mon, 7 Dec 2020 12:41:45 -0800 (PST) Received: from keithp.com (koto.keithp.com [10.0.0.2]) by elaine.keithp.com (Postfix) with ESMTPSA id 9400C3F2E1EB; Mon, 7 Dec 2020 12:41:45 -0800 (PST) Received: by keithp.com (Postfix, from userid 1000) id 6B54B15820DB; Mon, 7 Dec 2020 12:41:45 -0800 (PST) From: Keith Packard To: Jonathan Wakely , Vladimir V Cc: libstdc++@gcc.gnu.org Subject: Re: Problem building libstdc++ for the avr target In-Reply-To: <20201207203033.GI2309743@redhat.com> References: <20201207203033.GI2309743@redhat.com> Date: Mon, 07 Dec 2020 12:41:45 -0800 Message-ID: <87sg8h8i2e.fsf@keithp.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, 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: libstdc++@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libstdc++ mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Dec 2020 20:41:48 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Jonathan Wakely via Libstdc++ writes: >>and was resolved for the newlib. The fix was not applied for the avr-libc >>targets although the rationale behind the solution >>seems to be applicable there as well. I would like to ask what do you thi= nk >>about extending the scope of the solution to work >>with avr-libc based builds as well? > > Yes, I think it makes sense. I've been working on making libstdc++ work with picolibc, which shares a bunch of stdio code with avr-libc. I haven't tried my patches with avr-libc, but I wonder if that would be a good thing to do? With those patches, I'm able to use libstdc++'s iostream. =2D-=20 =2Dkeith --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAl/Ok4kACgkQ2yIaaQAA ABFyURAAkUF6ajaozHvRi1OIIjYZd/rnjYi47xcPzAeK9YD4zG0VUf36eAmELval a5th9WDf/F4MurHwCQLOY7mG+2OLi5fzhKvYYHJ5KD/macrHCo19ifSH8ZhB4s4q LZ1uFEJVlgorkgN2qp8VxskwtD7mF25XnLO5XJ86HS3TzQ5KgtN2ICjMnKdQdQ9I wrv7x+n0UuXl8sJAk0UPqU9SU7fPqmswOAG+gH+0A63RLch3vYjOYclNli1od8Q5 O3nfpWgRSGeBRrpLcTv9PVNKyvPLGIoEwlNMDWEky/F78uCwtJMlfe9o0zCZPOgg B/Bf/30Zr6GmdlYJ6Z313ojsKIUtiycd1Xj1d3/BtucWM9KDk1bu0TPwb5HWlfYm lKxGqfijSBHs5uxOB1DTITFcZ0uRioQvWWSBQC0djB7e01MweNcXh36xzNjZbN6U tT/O6XIoJnSHrVzFFZsn58UBnqGIYyGMMylbLtt1G6QY8pjQSQWpkg22h61XyKVs Pw8nrPLCMr5KGe09BYy/zktKXAdLTIgeSwA8piQ9IFnpMO/fdFWrJBtH90Aszt3G rVjF8dgU4NffXlovkeSERdqj+ljTKMDFfXfiUofgrOAO/ejANKgnxORL8pcXFOgs 8BP+9IEOKpQh3vZVwVQM4TfH5XQ+bbegvvlw+qDJkskSv36an4I= =ZgiW -----END PGP SIGNATURE----- --=-=-=--