public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Sergey Bugaev <bugaevc@gmail.com>
Cc: libc-alpha@sourceware.org, bug-hurd@gnu.org
Subject: Re: [PATCH 01/10] Remove sysdeps/generic/thread_state.h
Date: Wed, 17 May 2023 22:50:21 +0200	[thread overview]
Message-ID: <20230517205021.d36z3j6f2toqa5ac@begin> (raw)
In-Reply-To: <20230517191436.73636-2-bugaevc@gmail.com>

Sergey Bugaev, le mer. 17 mai 2023 22:14:27 +0300, a ecrit:
> This is a Mach-specific thread state definitions, and it's already
> handled by sysdeps/mach/thread_state.h.

?
No, this is the template file for the per-arch files, that you'd fall
down on when building for another arch, so you know what you're supposed
to fill in.

> Signed-off-by: Sergey Bugaev <bugaevc@gmail.com>
> ---
>  sysdeps/generic/thread_state.h | 51 ----------------------------------
>  1 file changed, 51 deletions(-)
>  delete mode 100644 sysdeps/generic/thread_state.h
> 
> diff --git a/sysdeps/generic/thread_state.h b/sysdeps/generic/thread_state.h
> deleted file mode 100644
> index 18926efb..00000000
> --- a/sysdeps/generic/thread_state.h
> +++ /dev/null
> @@ -1,51 +0,0 @@
> -/* Mach thread state definitions for machine-independent code.  Stub version.
> -   Copyright (C) 1994-2023 Free Software Foundation, Inc.
> -   This file is part of the GNU C Library.
> -
> -   The GNU C Library is free software; you can redistribute it and/or
> -   modify it under the terms of the GNU Lesser General Public
> -   License as published by the Free Software Foundation; either
> -   version 2.1 of the License, or (at your option) any later version.
> -
> -   The GNU C Library is distributed in the hope that it will be useful,
> -   but WITHOUT ANY WARRANTY; without even the implied warranty of
> -   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
> -   Lesser General Public License for more details.
> -
> -   You should have received a copy of the GNU Lesser General Public
> -   License along with the GNU C Library; if not, see
> -   <https://www.gnu.org/licenses/>.  */
> -
> -/* Everything else is called `thread_state', but CMU's header file is
> -   called `thread_status'.  Oh boy.  */
> -#include <mach/thread_state.h>
> -
> -/* Replace <machine> with "i386" or "mips" or whatever.  */
> -
> -/* This lets the kernel define architecture-specific registers for a new
> -   thread.  */
> -#define MACHINE_NEW_THREAD_STATE_FLAVOR	<machine>_NEW_THREAD_STATE
> -/* This makes the kernel load all architectures-specific registers for the
> -   thread.  */
> -#define MACHINE_THREAD_STATE_FLAVOR	<machine>_THREAD_STATE
> -#define MACHINE_THREAD_STATE_COUNT	<machine>_THREAD_STATE_COUNT
> -
> -#define machine_thread_state <machine>_thread_state
> -
> -/* Define these to the member names in `struct <machine>_thread_state'
> -   for the PC and stack pointer.  */
> -#define PC ?
> -#define SP ?
> -
> -/* This structure should contain all of the different flavors of thread
> -   state structures which are meaningful for this machine.  Every machine's
> -   definition of this structure should have a member `int set' which is a
> -   bit mask (1 << FLAVOR) of the flavors of thread state in the structure
> -   which are filled in; and a member `struct machine_thread_state basic'.
> -   On some machines those are the only members (e.g. i386); on others,
> -   there are several relevant flavors of thread state (e.g. mips).  */
> -struct machine_thread_all_state
> -  {
> -    int set;			/* Mask of bits (1 << FLAVOR).  */
> -    struct <machine>_thread_state basic;
> -  };
> -- 
> 2.40.1
> 
> 

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.

  reply	other threads:[~2023-05-17 20:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 19:14 [PATCH 00/10] Stack setup & misc fixes for x86_64-gnu Sergey Bugaev
2023-05-17 19:14 ` [PATCH 01/10] Remove sysdeps/generic/thread_state.h Sergey Bugaev
2023-05-17 20:50   ` Samuel Thibault [this message]
2023-05-17 19:14 ` [PATCH 02/10] mach: Define MACHINE_THREAD_STATE_SETUP_CALL Sergey Bugaev
2023-05-17 20:52   ` Samuel Thibault
2023-05-17 19:14 ` [PATCH 03/10] hurd: Use MACHINE_THREAD_STATE_SETUP_CALL Sergey Bugaev
2023-05-17 20:52   ` [PATCH 03/10] hurd: Use MACHINE_THREAD_STATE_SETUP_CALLo Samuel Thibault
2023-05-17 19:14 ` [PATCH 04/10] mach: Add __mach_setup_thread_call () Sergey Bugaev
2023-05-17 20:56   ` Samuel Thibault
2023-05-17 19:14 ` [PATCH 05/10] hurd: Use " Sergey Bugaev
2023-05-17 20:57   ` Samuel Thibault
2023-05-17 19:14 ` [RFC PATCH 06/10] hurd: Make sure to not use tcb->self Sergey Bugaev
2023-05-17 20:59   ` Samuel Thibault
2023-05-18 18:55     ` Joseph Myers
2023-05-18 19:33       ` Sergey Bugaev
2023-05-18 20:16         ` Joseph Myers
2023-05-18 23:47           ` Samuel Thibault
2023-05-19  8:22           ` Sergey Bugaev
2023-05-19  9:39             ` Florian Weimer
2023-05-19 16:50             ` Joseph Myers
2023-05-19 14:47           ` [PATCH] hurd: Fix using interposable hurd_thread_self Sergey Bugaev
2023-05-19 18:57             ` Samuel Thibault
2023-05-17 19:14 ` [PATCH 07/10] hurd: Fix x86_64 _hurd_tls_fork Sergey Bugaev
2023-05-17 21:01   ` Samuel Thibault
2023-05-17 19:14 ` [PATCH 08/10] hurd: Fix setting up pthreads Sergey Bugaev
2023-05-17 21:02   ` Samuel Thibault
2023-05-17 19:14 ` [PATCH 09/10] hurd: Also make it possible to call strlen very early Sergey Bugaev
2023-05-17 21:04   ` Samuel Thibault
2023-05-17 19:14 ` [RFC PATCH 10/10] hurd: Regenerate errno.h Sergey Bugaev
2023-05-17 19:39   ` Joseph Myers
2023-05-17 21:04     ` 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=20230517205021.d36z3j6f2toqa5ac@begin \
    --to=samuel.thibault@gnu.org \
    --cc=bug-hurd@gnu.org \
    --cc=bugaevc@gmail.com \
    --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).