From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by sourceware.org (Postfix) with ESMTP id 6F090395C41D for ; Mon, 7 Dec 2020 21:07:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 6F090395C41D Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-584-GV4nn3OmMzKyaGlwm_F7Tw-1; Mon, 07 Dec 2020 16:07:01 -0500 X-MC-Unique: GV4nn3OmMzKyaGlwm_F7Tw-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 794CD1005504; Mon, 7 Dec 2020 21:07:00 +0000 (UTC) Received: from localhost (unknown [10.33.36.246]) by smtp.corp.redhat.com (Postfix) with ESMTP id 191B139A5F; Mon, 7 Dec 2020 21:06:59 +0000 (UTC) Date: Mon, 7 Dec 2020 21:06:59 +0000 From: Jonathan Wakely To: Keith Packard Cc: Vladimir V , libstdc++@gcc.gnu.org Subject: Re: Problem building libstdc++ for the avr target Message-ID: <20201207210659.GK2309743@redhat.com> References: <20201207203033.GI2309743@redhat.com> <87sg8h8i2e.fsf@keithp.com> MIME-Version: 1.0 In-Reply-To: <87sg8h8i2e.fsf@keithp.com> X-Clacks-Overhead: GNU Terry Pratchett X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spam-Status: No, score=-7.9 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, 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 21:07:06 -0000 On 07/12/20 12:41 -0800, Keith Packard via Libstdc++ wrote: >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 think >>>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. That might be interesting to try. I'm very much in favour of changes to libstdc++ that allow it to be used on small systems. While some C++ features may not be suitable for those systems, I think there's a lot of the standard library that is still useful, but isn't part of the current "freestanding" subset. And I'd like libstdc++ to be able to scale from very small to very large, rather than needing to fork it to meet those needs.