From: Jonathan Wakely <jwakely@redhat.com>
To: gcc-patches@gcc.gnu.org, bug-hurd@gnu.org
Cc: libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Introduce GNU/Hurd-specific libstdc++ os-defines.h
Date: Fri, 7 Oct 2022 12:14:26 +0100 [thread overview]
Message-ID: <Y0AKEvpETLp9vSg/@redhat.com> (raw)
In-Reply-To: <20220829003040.kfgr7epzzyavbsjm@begin>
As documented at https://gcc.gnu.org/lists.html all patches for
libstdc++ need to be CC'd to the libstdc++ list. That's why your patch
has not been reviewed, because I didn't see it.
On 29/08/22 02:30 +0200, Samuel Thibault wrote:
>This is notably needed because in glibc 2.34, the move of pthread functions
>into libc.so happened for Linux only, not GNU/Hurd.
>
>The pthread_self() function can also always be used fine as it is.
>
>libstdc++-v3/ChangeLog:
>
> * config/os/gnu/os_defines.h: New file.
> * config/os/gnu/ctype_base.h: New file.
> * config/os/gnu/ctype_configure_char.cc: New file.
> * config/os/gnu/ctype_inline.h: New file.
> * configure.host: On gnu* host, use os/gnu instead of os/gnu-linux.
I think the commit message should note that these files are all copied
from the existing gnu-linux ones, so that the git log records that and
people don't need to compare them manually.
But if these files are all identical to the existing gnu-linux ones,
except for a couple of macros in os_defines.h being conditional on
Linux, why not just test __linux__ in os_defines.h?
Do we need three new ctype files that are identical to existing files?
Why maintain two copies of the same code?
>diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
>index ba5939d9003..dd288cce2ca 100644
>--- a/libstdc++-v3/ChangeLog
>+++ b/libstdc++-v3/ChangeLog
>@@ -1,3 +1,11 @@
>+2022-08-28 Samuel Thibault <samuel.thibault@ens-lyon.org>
>+
>+ * config/os/gnu/os_defines.h: New file.
>+ * config/os/gnu/ctype_base.h: New file.
>+ * config/os/gnu/ctype_configure_char.cc: New file.
>+ * config/os/gnu/ctype_inline.h: New file.
>+ * configure.host: On gnu* host, use os/gnu instead of os/gnu-linux.
>+
Please do not include ChangeLog diffs in the patch, it just means the
patch can't be applied cleanly. GCC changelogs are auto-generated
every night. The ChangeLog entry should be submitted as plain text not
inthe diff, or just make it part of your Git commit message.
https://gcc.gnu.org/contribute.html#patches
next prev parent reply other threads:[~2022-10-07 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 0:30 Samuel Thibault
2022-09-17 21:55 ` Samuel Thibault
2022-10-07 11:14 ` Jonathan Wakely [this message]
2022-10-07 20:43 ` Samuel Thibault
2022-10-23 9:34 ` [PATCH]: Fix static-pie on Hurd target Samuel Thibault
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=Y0AKEvpETLp9vSg/@redhat.com \
--to=jwakely@redhat.com \
--cc=bug-hurd@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).