From: Zack Weinberg <zackw@panix.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/2] Remove _IO_MTSAFE_IO from public headers.
Date: Thu, 06 Apr 2017 20:41:00 -0000 [thread overview]
Message-ID: <CAKCAbMi0zu84hEJ+=tGC8ZWa=5t9k0Suq6g5HaDaY9gtsMPDGw@mail.gmail.com> (raw)
In-Reply-To: <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)
next prev parent reply other threads:[~2017-04-06 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 12:55 [PATCH 0/2] _ISOMAC testsuite round N Zack Weinberg
2017-03-22 12:55 ` [PATCH 1/2] Remove _IO_MTSAFE_IO from public headers Zack Weinberg
2017-04-06 20:29 ` Adhemerval Zanella
2017-04-06 20:41 ` Zack Weinberg [this message]
2017-04-06 21:30 ` Adhemerval Zanella
2017-04-06 22:06 ` Florian Weimer
2017-04-07 14:46 ` Adhemerval Zanella
2017-03-22 12:55 ` [PATCH 2/2] Suppress internal declarations for most of the testsuite Zack Weinberg
2017-05-08 14:02 ` Andreas Schwab
2017-05-08 20:02 ` Zack Weinberg
2017-05-09 7:57 ` Andreas Schwab
2017-05-09 11:25 ` Zack Weinberg
2017-04-06 16:12 ` [PATCH 0/2] _ISOMAC testsuite round N Zack Weinberg
2017-04-17 14:31 ` Zack Weinberg
2017-05-01 11:24 ` Zack Weinberg
2017-05-08 13:23 ` Zack Weinberg
-- strict thread matches above, loose matches on Subject: below --
2017-03-08 16:30 [PATCH 0/2] Revised _ISOMAC testsuite patches Zack Weinberg
2017-03-08 16:35 ` [PATCH 1/2] Remove _IO_MTSAFE_IO from public headers Zack Weinberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKCAbMi0zu84hEJ+=tGC8ZWa=5t9k0Suq6g5HaDaY9gtsMPDGw@mail.gmail.com' \
--to=zackw@panix.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).