From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 103217 invoked by alias); 29 Jun 2018 14:49:08 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 88103 invoked by uid 89); 29 Jun 2018 14:48:51 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=H*MI:4ca3, H*M:4ca3, HContent-Transfer-Encoding:8bit X-HELO: mx1.redhat.com To: GNU C Library , "Gabriel F. T. Gomes" From: Florian Weimer Subject: Legacy _IO_* symbols and Flaot128 transition Message-ID: Date: Fri, 29 Jun 2018 14:49:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2018-06/txt/msg00987.txt.bz2 libio exports a bunch of symbols for historic reasons: _IO_fprintf _IO_printf _IO_sprintf _IO_sscanf _IO_vfprintf _IO_vfscanf _IO_vsprintf These aren't compat symbols yet, but will not be in installed headers for glibc 2.28. Zack's cleanup patches only turns _IO_vfscanf into a compat symbol (in “Add __vfscanf_internal and __vfwscanf_internal with flags arguments.”). I think we should turn all of them into compat symbols and drop their compatibility wrappers from nldbl_nonshared.a, and avoid adding binary128 compatibility wrappers for them. I can work on a patch if that would help. Comments? Thanks, Florian