This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 1/2] Remove _IO_MTSAFE_IO from public headers.
- From: Zack Weinberg <zackw at panix dot com>
- To: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 6 Apr 2017 16:41:25 -0400
- Subject: Re: [PATCH 1/2] Remove _IO_MTSAFE_IO from public headers.
- Authentication-results: sourceware.org; auth=none
- References: <20170322125504.4863-1-zackw@panix.com> <20170322125504.4863-2-zackw@panix.com> <adec0591-dec4-c2f0-5a70-c96a934c7c3b@linaro.org>
On Thu, Apr 6, 2017 at 4:29 PM, Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
> On 22/03/2017 09:55, Zack Weinberg wrote:
>> _IO_MTSAFE_IO controls whether stdio is *built* with support for
>> multithreading. In the distant past it might also have worked as a
>> feature selection macro, allowing library *users* to select
>> thread-safe or lock-free stdio at application build time, I haven't
>> done the archaeology. Nowadays, defining _IO_MTSAFE_IO while using
>> the installed headers, or in _ISOMAC mode, will cause libio.h to throw
>> syntax errors.
>
> What prevent us to just get rid of _IO_MTSAFE_IO and just build/assume
> stdio with multithread support?
I think that's a desirable goal, but I don't want to do that in this
patchset because I suspect it will be messy *inside* libc. And I'd
start by getting it out of the public headers, anyway.
(I'd like to stop installing libio.h at all, too, but that's probably
going to be nastier:
https://codesearch.debian.net/search?q=libio.h&perpkg=1)