Problem building libstdc++ for the avr target

[Jonathan Wakely]

On 07/12/20 12:41 -0800, Keith Packard via Libstdc++ wrote:
>Jonathan Wakely via Libstdc++ <libstdc++@gcc.gnu.org> 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.