public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: 刘振松 <liuzhensong@loongson.cn>
To: "Xi Ruoyao" <xry111@xry111.site>
Cc: "WANG Xuerui" <i.swmail@xen0n.name>,
	caiyinyu <caiyinyu@loongson.cn>,
	 adhemerval.zanella@linaro.org, libc-alpha@sourceware.org,
	 joseph_myers@mentor.com, carlos@redhat.com
Subject: Re: Re: [PATCH v7 00/13] GLIBC LoongArch PATCHES
Date: Mon, 25 Jul 2022 09:58:41 +0800 (GMT+08:00)	[thread overview]
Message-ID: <6e4016e7.8a14.1823313f163.Coremail.liuzhensong@loongson.cn> (raw)
In-Reply-To: <71ad82b8b669d4233b7fd4741add7b58bd7ac20e.camel@xry111.site>




&gt; -----原始邮件-----
&gt; 发件人: "Xi Ruoyao" <xry111@xry111.site>
&gt; 发送时间: 2022-07-24 19:51:51 (星期日)
&gt; 收件人: "WANG Xuerui" <i.swmail@xen0n.name>, caiyinyu <caiyinyu@loongson.cn>, adhemerval.zanella@linaro.org, libc-alpha@sourceware.org, joseph_myers@mentor.com, carlos@redhat.com
&gt; 抄送: liuzhensong@loongson.cn
&gt; 主题: Re: [PATCH v7 00/13] GLIBC LoongArch PATCHES
&gt; 
&gt; On Sun, 2022-07-24 at 17:49 +0800, WANG Xuerui wrote:
&gt; 
&gt; &gt; Of these, the ifunc failures are "expected" by you, the 
&gt; &gt; elf/check-abi-libc diff is trivial (maybe you just didn't rebase as 
&gt; &gt; frequently):
&gt; &gt; 
&gt; &gt; --- ../sysdeps/unix/sysv/linux/loongarch/lp64/libc.abilist 2022-07-23 
&gt; &gt; 14:45:57.490029442 +0800
&gt; &gt; +++ /home/xenon/src/glibc/build/libc.symlist&nbsp;&nbsp;&nbsp; 2022-07-24 
&gt; &gt; 13:44:10.416642655 +0800
&gt; &gt; @@ -496 +496 @@ GLIBC_2.36 _mcount F
&gt; &gt; -GLIBC_2.36 _nl_default_dirname D 0x12
&gt; &gt; +GLIBC_2.36 _nl_default_dirname D 0x17
&gt; &gt; @@ -541,0 +542,3 @@ GLIBC_2.36 alphasort64 F
&gt; &gt; +GLIBC_2.36 arc4random F
&gt; &gt; +GLIBC_2.36 arc4random_buf F
&gt; &gt; +GLIBC_2.36 arc4random_uniform F
&gt; 
&gt; arc4random is just merged two days ago.
&gt; 
&gt; &gt; The others may need some love. Of course they're possibly because of my 
&gt; &gt; particular environment (Gentoo is a little bit different than "ordinary" 
&gt; &gt; distros like Debian/Fedora, and I already have to symlink the 
&gt; &gt; libgcc_s.so and libstdc++.so to pass the nptl tests at all)
&gt; 
&gt; I can tell tst-nss-files-hosts-long is most likely PR24816.  For the
&gt; others I'm not sure.
&gt; 
&gt; By "symlink libgcc_s.so and libstdc++.so" I guess you are running tests
&gt; in a temporary system ("Gentoo stage 1" IIRC).  In LFS we also get some
&gt; additional test failures in the temporary system [1] so it's better to
&gt; rerun the tests in a full system.
&gt; 
&gt; (In earlier LFS releases we also needed to symlink libgcc_s.so and
&gt; libstdc++.so for glibc tests, but it's no longer needed now thanks to a
&gt; major refactoring [2].)
&gt; 
&gt; [1]: https://www.linuxfromscratch.org/lfs/view/systemd/chapter08/glibc.html
&gt; [2]: https://lists.linuxfromscratch.org/sympa/arc/lfs-dev/2020-05/msg00000.html
&gt; 
&gt; My test result on LFS (fully built) with a patched ld seems clean.  The
&gt; patch is originally published at
&gt; https://sourceware.org/pipermail/binutils/2022-July/121852.html, but
&gt; it's in a large series introducing new relocation types.  I managed to
&gt; rebased and adjusted the patch so it can be applied individually for
&gt; binutils-gdb master branch.  The patch is attached in this mail.
&gt; 
&gt; +Zhensong: is there any possibility to merge this patch for binutils
&gt; master and 2.39 release branch (including 2.38 release branch would be
&gt; even better) so at least glibc ifunc tests will be happy?

This patch alone has not been fully tested, some ifunc implementations rely on new modifications.
If there is no problem with the tests, it can be merged into other branchs.

&gt; 
&gt; XPASS: conform/UNIX98/ndbm.h/linknamespace
&gt; XPASS: conform/XOPEN2K/ndbm.h/linknamespace
&gt; XPASS: conform/XOPEN2K8/ndbm.h/linknamespace
&gt; XPASS: conform/XPG42/ndbm.h/linknamespace
&gt; UNSUPPORTED: crypt/cert
&gt; FAIL: elf/check-abi-libc
&gt; UNSUPPORTED: elf/tst-env-setuid
&gt; UNSUPPORTED: elf/tst-env-setuid-tunables
&gt; XPASS: elf/tst-protected1a
&gt; XPASS: elf/tst-protected1b
&gt; UNSUPPORTED: elf/tst-valgrind-smoke
&gt; UNSUPPORTED: misc/tst-adjtimex
&gt; UNSUPPORTED: misc/tst-clock_adjtime
&gt; UNSUPPORTED: misc/tst-ntp_adjtime
&gt; UNSUPPORTED: misc/tst-pkey
&gt; UNSUPPORTED: misc/tst-rseq
&gt; UNSUPPORTED: misc/tst-rseq-disable
&gt; UNSUPPORTED: nptl/test-cond-printers
&gt; UNSUPPORTED: nptl/test-condattr-printers
&gt; UNSUPPORTED: nptl/test-mutex-printers
&gt; UNSUPPORTED: nptl/test-mutexattr-printers
&gt; UNSUPPORTED: nptl/test-rwlock-printers
&gt; UNSUPPORTED: nptl/test-rwlockattr-printers
&gt; UNSUPPORTED: nptl/tst-pthread-gdb-attach
&gt; UNSUPPORTED: nptl/tst-pthread-gdb-attach-static
&gt; UNSUPPORTED: nptl/tst-rseq-nptl
&gt; UNSUPPORTED: stdlib/tst-secure-getenv
&gt; UNSUPPORTED: time/tst-clock_settime
&gt; UNSUPPORTED: time/tst-settimeofday
&gt; Summary of test results:
&gt;       1 FAIL
&gt;    4576 PASS
&gt;      22 UNSUPPORTED
&gt;      12 XFAIL
&gt;       6 XPASS
&gt; 
&gt; 
&gt; -- 
&gt; Xi Ruoyao <xry111@xry111.site>
&gt; School of Aerospace Science and Technology, Xidian University
</xry111@xry111.site></caiyinyu@loongson.cn></i.swmail@xen0n.name></xry111@xry111.site>

本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件通知发件人并删除本邮件。 
This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it. 

  parent reply	other threads:[~2022-07-25  1:58 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19  1:20 caiyinyu
2022-07-19  1:20 ` [PATCH v7 01/13] LoongArch: Add LoongArch entries to config.h.in caiyinyu
2022-07-21 21:02   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 02/13] LoongArch: Add relocations and ELF flags to elf.h and scripts/glibcelf.py caiyinyu
2022-07-21 21:02   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 03/13] LoongArch: ABI Implementation caiyinyu
2022-07-20 12:29   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 04/13] LoongArch: Thread-Local Storage Support caiyinyu
2022-07-20 14:34   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 05/13] LoongArch: Generic <math.h> and soft-fp Routines caiyinyu
2022-07-20 13:04   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 06/13] LoongArch: Atomic and Locking Routines caiyinyu
2022-07-20 14:32   ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 07/13] LoongArch: Linux Syscall Interface caiyinyu
2022-07-20 14:35   ` Adhemerval Zanella Netto
2022-07-27  5:27   ` WANG Xuerui
2022-07-27  5:32     ` WANG Xuerui
2022-07-27 11:16       ` Adhemerval Zanella Netto
2022-07-27 13:01         ` WANG Xuerui
2022-07-27 19:22           ` Adhemerval Zanella Netto
2022-07-19  1:20 ` [PATCH v7 08/13] LoongArch: Linux ABI caiyinyu
2022-07-20 16:37   ` Adhemerval Zanella Netto
2022-07-20 17:19 ` [PATCH v7 00/13] GLIBC LoongArch PATCHES Adhemerval Zanella Netto
2022-07-21  2:44   ` caiyinyu
2022-07-24  9:49 ` WANG Xuerui
2022-07-24 11:51   ` Xi Ruoyao
2022-07-24 12:02     ` WANG Xuerui
2022-07-25  8:21       ` caiyinyu
2022-07-25  8:28         ` Xi Ruoyao
2022-07-25  1:58     ` 刘振松 [this message]
2022-07-25  8:01       ` Xi Ruoyao
2022-07-25 13:27   ` Adhemerval Zanella Netto
2022-07-25 14:14     ` caiyinyu
2022-07-26 12:35       ` caiyinyu
2022-07-26 12:42         ` Adhemerval Zanella Netto
2022-07-26 14:00           ` Mark Wielaard

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=6e4016e7.8a14.1823313f163.Coremail.liuzhensong@loongson.cn \
    --to=liuzhensong@loongson.cn \
    --cc=adhemerval.zanella@linaro.org \
    --cc=caiyinyu@loongson.cn \
    --cc=carlos@redhat.com \
    --cc=i.swmail@xen0n.name \
    --cc=joseph_myers@mentor.com \
    --cc=libc-alpha@sourceware.org \
    --cc=xry111@xry111.site \
    /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).