public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: caiyinyu <caiyinyu@loongson.cn>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	libc-alpha@sourceware.org
Cc: xuchenghua@loongson.cn, joseph_myers@mentor.com
Subject: Re: [PATCH v2 09/14] LoongArch: Linux ABI
Date: Fri, 15 Apr 2022 09:28:50 +0800	[thread overview]
Message-ID: <a703a4cb-b88f-7136-990f-761f1e4ce060@loongson.cn> (raw)
In-Reply-To: <0446048b-ba32-f750-6e00-1fde5bb435f1@linaro.org>


在 2022/1/4 下午10:24, Adhemerval Zanella 写道:
> On 31/12/2021 03:44, caiyinyu wrote:
>
>> diff --git a/sysdeps/loongarch/nptl/bits/struct_rwlock.h b/sysdeps/loongarch/nptl/bits/struct_rwlock.h
>> new file mode 100644
>> index 0000000000..12b6a469bd
>> --- /dev/null
>> +++ b/sysdeps/loongarch/nptl/bits/struct_rwlock.h
>> @@ -0,0 +1,44 @@
>> +/* LoongArch internal rwlock struct definitions.
>> +   Copyright (C) 2021 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/>.  */
>> +
>> +#ifndef _RWLOCK_INTERNAL_H
>> +#define _RWLOCK_INTERNAL_H
>> +
>> +/* There is a lot of padding in this structure.  While it's not strictly
>> +   necessary on LoongArch, we're going to leave it in to be on the safe side in
>> +   case it's needed in the future.  Most other architectures have the padding,
>> +   so this gives us the same extensibility as everyone else has.  */
>> +struct __pthread_rwlock_arch_t
>> +{
>> +  unsigned int __readers;
>> +  unsigned int __writers;
>> +  unsigned int __wrphase_futex;
>> +  unsigned int __writers_futex;
>> +  unsigned int __pad3;
>> +  unsigned int __pad4;
>> +  int __cur_writer;
>> +  int __shared;
>> +  unsigned long int __pad1;
>> +  unsigned long int __pad2;
>> +  unsigned int __flags;
>> +};
>> +
>> +#define __PTHREAD_RWLOCK_INITIALIZER(__flags) \
>> +  0, 0, 0, 0, 0, 0, 0, 0, 0, 0, __flags
>> +
>> +#endif
> Why can't you use the generic Linux sysdeps/nptl/bits/struct_rwlock.h ?
Fixed by using generic Linux file.
>> diff --git a/sysdeps/loongarch/nptl/pthread-offsets.h b/sysdeps/loongarch/nptl/pthread-offsets.h
>> new file mode 100644
>> index 0000000000..415c3c113f
>> --- /dev/null
>> +++ b/sysdeps/loongarch/nptl/pthread-offsets.h
>> @@ -0,0 +1,15 @@
>> +#if __WORDSIZE == 64
>> +#define __PTHREAD_MUTEX_KIND_OFFSET 16
>> +#else
>> +#define __PTHREAD_MUTEX_KIND_OFFSET 12
>> +#endif
>> +
>> +#if __WORDSIZE == 64
>> +#define __PTHREAD_RWLOCK_FLAGS_OFFSET 48
>> +#else
>> +#if __BYTE_ORDER == __BIG_ENDIAN
>> +#define __PTHREAD_RWLOCK_FLAGS_OFFSET 27
>> +#else
>> +#define __PTHREAD_RWLOCK_FLAGS_OFFSET 24
>> +#endif
>> +#endif
> Ditto.
Fixed by using generic Linux file.


  reply	other threads:[~2022-04-15  1:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31  6:44 [PATCH v2 00/14] GLIBC LoongArch PATCHES caiyinyu
2021-12-31  6:44 ` [PATCH v2 01/14] LoongArch: Update NEWS and README for the LoongArch port caiyinyu
2022-01-04 13:30   ` Adhemerval Zanella
2022-04-15  1:28     ` caiyinyu
2021-12-31  6:44 ` [PATCH v2 02/14] LoongArch: Add LoongArch entries to config.h.in caiyinyu
2021-12-31  6:44 ` [PATCH v2 03/14] LoongArch: Add relocations and ELF flags to elf.h caiyinyu
2021-12-31  6:44 ` [PATCH v2 04/14] LoongArch: ABI Implementation caiyinyu
2022-01-04 13:46   ` Adhemerval Zanella
2022-04-15  1:28     ` caiyinyu
2021-12-31  6:44 ` [PATCH v2 05/14] LoongArch: Thread-Local Storage Support caiyinyu
2022-01-04 14:01   ` Adhemerval Zanella
2022-04-15  1:28     ` caiyinyu
2021-12-31  6:44 ` [PATCH v2 06/14] LoongArch: Generic <math.h> and soft-fp Routines caiyinyu
2022-01-04 14:05   ` Adhemerval Zanella
2022-01-04 20:31     ` Joseph Myers
2021-12-31  6:44 ` [PATCH v2 07/14] LoongArch: Atomic and Locking Routines caiyinyu
2022-01-04 14:09   ` Adhemerval Zanella
2022-04-15  1:28     ` caiyinyu
2021-12-31  6:44 ` [PATCH v2 08/14] LoongArch: Linux Syscall Interface caiyinyu
2022-01-04 14:20   ` Adhemerval Zanella
2022-04-15  1:28     ` caiyinyu
2021-12-31  6:44 ` [PATCH v2 09/14] LoongArch: Linux ABI caiyinyu
2021-12-31 17:37   ` Joseph Myers
2022-04-15  1:27     ` caiyinyu
2022-01-04 14:24   ` Adhemerval Zanella
2022-04-15  1:28     ` caiyinyu [this message]
2021-12-31  6:44 ` [PATCH v2 10/14] LoongArch: Linux Startup and Dynamic Loading Code caiyinyu
2022-01-04 14:27   ` Adhemerval Zanella
2022-04-15  1:28     ` caiyinyu
2021-12-31  6:44 ` [PATCH v2 11/14] LoongArch: Add ABI Lists caiyinyu
2021-12-31 17:43   ` Joseph Myers
2022-04-15  1:27     ` caiyinyu
2021-12-31  6:44 ` [PATCH v2 12/14] LoongArch: Build Infastructure caiyinyu
2022-01-04 14:33   ` Adhemerval Zanella
2021-12-31  6:44 ` [PATCH v2 13/14] LoongArch: Hard Float Support caiyinyu
2021-12-31 17:47   ` Joseph Myers
2022-04-15  1:27     ` caiyinyu
2021-12-31  6:44 ` [PATCH v2 14/14] LoongArch: Update build-many-glibcs.py for the LoongArch Port caiyinyu
2021-12-31 17:34 ` [PATCH v2 00/14] GLIBC LoongArch PATCHES Joseph Myers
2022-04-15  1:27   ` caiyinyu
2022-01-04 13:27 ` Adhemerval Zanella
2022-04-15  1:28   ` caiyinyu

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=a703a4cb-b88f-7136-990f-761f1e4ce060@loongson.cn \
    --to=caiyinyu@loongson.cn \
    --cc=adhemerval.zanella@linaro.org \
    --cc=joseph_myers@mentor.com \
    --cc=libc-alpha@sourceware.org \
    --cc=xuchenghua@loongson.cn \
    /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).