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 [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 1A1EF385B518 for ; Tue, 2 May 2023 15:50:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1A1EF385B518 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1683042622; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=hIj+F39RMT79VTkJe7ClsDaAbXP1ZnG+vgwZMKqpXfU=; b=XJI6efans2iO7x8va8gpvV3vPVhXm1ZBvFqGijHoLF/olT69IvhbUqAC9WmFSaYP4KRDLN /uiJ2XkVuEmFZenBN6APwQLHg0jeJv+9O4O3pZdXBzT/Dw43nlqVVQYIb6ZOsT8yKRHkbE qa/8WZiM8Dts4UoYC1D5ir7gE9G8R2c= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-654-iRV418ilOSSyhQZJzw7hpw-1; Tue, 02 May 2023 11:50:21 -0400 X-MC-Unique: iRV418ilOSSyhQZJzw7hpw-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D634F811E7D; Tue, 2 May 2023 15:50:20 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.39.194.156]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 987FDC15BAD; Tue, 2 May 2023 15:50:20 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 342FoI863181343 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Tue, 2 May 2023 17:50:18 +0200 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 342FoIk83181342; Tue, 2 May 2023 17:50:18 +0200 Date: Tue, 2 May 2023 17:50:17 +0200 From: Jakub Jelinek To: Jonathan Wakely Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: [PATCH] libstdc++: Regenerate baseline_symbols.txt files for Linux Message-ID: Reply-To: Jakub Jelinek References: MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-3.4 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_H2,SPF_HELO_NONE,SPF_NONE,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 Tue, May 02, 2023 at 04:42:52PM +0100, Jonathan Wakely wrote: > On Tue, 2 May 2023 at 09:45, Jakub Jelinek wrote: > > > Hi! > > > > The following patch regenerates the ABI files (I've only changed the > > Linux files which were updated recently (last month)). > > > > Tested on x86_64-linux, ok for trunk and later 13.2? > > > > OK, thanks. > > I currently get: > FAIL: libstdc++-abi/abi_check > on powerpc64le for old glibc, with the _Float128 overloads for > std::from_chars and std::to_chars. I'll try to regenerate it from latest Fedora build for ppc64le. > Those symbols were OK when GLIBCXX_3.4.31 was the latest, because added > symbols in the latest version are OK. Now that GLIBCXX_3.4.32 is the > latest, we can't have additions to the older version. Jakub