From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jwakely@redhat.com>
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 95A4C3858001
 for <libstdc++@gcc.gnu.org>; Thu, 25 Mar 2021 23:02:58 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 95A4C3858001
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-564-Bb3LAut0PD2gwDR8VQy0Eg-1; Thu, 25 Mar 2021 19:02:56 -0400
X-MC-Unique: Bb3LAut0PD2gwDR8VQy0Eg-1
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com
 [10.5.11.14])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 5FC60801817;
 Thu, 25 Mar 2021 23:02:55 +0000 (UTC)
Received: from localhost (unknown [10.33.36.164])
 by smtp.corp.redhat.com (Postfix) with ESMTP id F32385D9CA;
 Thu, 25 Mar 2021 23:02:54 +0000 (UTC)
Date: Thu, 25 Mar 2021 23:02:54 +0000
From: Jonathan Wakely <jwakely@redhat.com>
To: Vladimir V <vv.os.swe@gmail.com>
Cc: libstdc++@gcc.gnu.org
Subject: Re: Problem building libstdc++ for the avr target
Message-ID: <20210325230254.GV3008@redhat.com>
References: <CA+=iAirEbHa95-QTJtqBFA4m8ZsmYYMHpHhwtox7Hp3Avv7fAg@mail.gmail.com>
 <20210208174539.GN3008@redhat.com>
 <20210208174707.GO3008@redhat.com>
 <CA+=iAirNQKf4UBtXAbCLHomuaoQyBL=p4jrHiO7v2wzWCCGJaA@mail.gmail.com>
 <20210209104756.GW3008@redhat.com>
 <CA+=iAipEgzncQ5zPUQOT4m_JSGHhTdrnMCWySQVCog0HG7aBaA@mail.gmail.com>
 <CA+=iAipaM6VQWBH3gWsrAjy=hB8ss_ZpRyWjPge2SJ7bxmEEOQ@mail.gmail.com>
 <20210325123603.GN3008@redhat.com>
 <20210325182709.GU3008@redhat.com>
 <CA+=iAioVbpTsPAz+1aoBpDy86_hBkkrfa8dLkDGmTn3eJxMbaQ@mail.gmail.com>
MIME-Version: 1.0
In-Reply-To: <CA+=iAioVbpTsPAz+1aoBpDy86_hBkkrfa8dLkDGmTn3eJxMbaQ@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14
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=-8.0 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW,
 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 <libstdc++.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/libstdc++>,
 <mailto:libstdc++-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/libstdc++/>
List-Post: <mailto:libstdc++@gcc.gnu.org>
List-Help: <mailto:libstdc++-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/libstdc++>,
 <mailto:libstdc++-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2021 23:03:01 -0000

On 25/03/21 22:37 +0100, Vladimir V via Libstdc++ wrote:
>Thank you for the quick reply.
>
>I am wondering if the freestanding libstdc++ requires that only
>freestanding subset of the underlying libc is used?

The freestanding library is always allowed to provide more features
than the minimum set required. So it is certainly possible to expose
the whole of the libc <stdlib.h> through <cstdlib> if we wish to.

We shouldn't do that at this stage of the GCC 11 cycle but we could
consider it for GCC 12.

Does the change I pushed earlier solve your build error with
new_opa.cc though?