From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v4 2/2] gcc: Drop obsolete INCLUDE_PTHREAD_H
Date: Tue, 14 Mar 2023 08:44:10 -0600 [thread overview]
Message-ID: <78f2b8fe-a8aa-fe17-947f-d576de3834c9@gmail.com> (raw)
In-Reply-To: <CA+yXCZDVsUJKjABkqxnxNWu+Z96cHKdirm0Ov+ase1utN7A_0w@mail.gmail.com>
On 3/14/23 07:45, Kito Cheng via Gcc-patches wrote:
> It's not the RISC-V part, so this requires a global maintainer there I think?
It does. I hadn't had a chance to dig into the history of the pthread.h
include to understand why it was originally included which would be the
first step in determining if it's actually safe to remove.
Jeff
next prev parent reply other threads:[~2023-03-14 14:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 0:23 [PATCH v4 1/2] RISC-V: Avoid calloc() poisoning on musl Sam James
2023-03-14 0:23 ` [PATCH v4 2/2] gcc: Drop obsolete INCLUDE_PTHREAD_H Sam James
2023-03-14 0:27 ` juzhe.zhong
2023-03-14 13:45 ` Kito Cheng
2023-03-14 14:44 ` Jeff Law [this message]
2023-03-31 18:44 ` [PATCH v4 2/2] gcc: Drop obsolete INCLUDE_PTHREAD_H (ping) Sam James
2023-04-02 19:54 ` Jeff Law
2023-04-02 20:06 ` Andrew Pinski
2023-04-02 20:07 ` Jeff Law
2023-04-02 20:13 ` Andrew Pinski
2023-04-02 20:16 ` Sam James
2023-03-14 9:06 ` [PATCH v4 1/2] RISC-V: Avoid calloc() poisoning on musl Richard Biener
2023-03-14 13:44 ` Kito Cheng
2023-03-14 13:48 ` Kito Cheng
2023-03-14 22:06 ` Sam James
2023-03-14 21:39 ` Sam James
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=78f2b8fe-a8aa-fe17-947f-d576de3834c9@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.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).