From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: "Wang, Yanzhang" <yanzhang.wang@intel.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] RISC-V: Enable static-pie.
Date: Tue, 15 Aug 2023 08:46:02 -0300 [thread overview]
Message-ID: <26bd6001-6ff5-dcab-d233-9adb6b8efb6f@linaro.org> (raw)
In-Reply-To: <IA1PR11MB64666505A9583172D323D8EBF216A@IA1PR11MB6466.namprd11.prod.outlook.com>
On 13/08/23 09:20, Wang, Yanzhang via Libc-alpha wrote:
> Hi Palmer,
>
> I have tested the commit(542b110585) with this patch. The results like below,
>
> Summary of test results:
> 189 FAIL
> 4328 PASS
> 101 UNSUPPORTED
> 16 XFAIL
> 2 XPASS
>
> And the commit(542b110585)'s results like below,
>
> Summary of test results:
> 189 FAIL
> 4326 PASS
> 101 UNSUPPORTED
> 16 XFAIL
> 2 XPASS
>
> The binutils's commit is 2db20b97f1d and gcc's commit is bf36656a14a.
>
> I use the command make check-glibc-linux in riscv-gnu-toolchain. Not sure is
> that acceptable.
The riscv reports for 2.38 release [1] list at maximum of 6 FAIL for all
the ABI variants. The 189 failures you are reporting means that your
environment is either missing some setup (for instance, copying the
libgcc_s.so and libstd++.so on the build folder so C++ and tests that
require pthread_cancel or backtrace works correctly) or it is not
properly configured.
Please sort this out first, since with that amount of failures is not
straightforward to check whether static-pie is really working as
intended.
next prev parent reply other threads:[~2023-08-15 11:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 23:33 yanzhang.wang
2023-08-11 1:57 ` Palmer Dabbelt
2023-08-13 12:20 ` Wang, Yanzhang
2023-08-15 11:46 ` Adhemerval Zanella Netto [this message]
2023-09-09 3:17 ` Wang, Yanzhang
2023-09-09 3:30 ` Palmer Dabbelt
2023-09-09 6:54 ` Wang, Yanzhang
2023-09-11 14:14 ` Palmer Dabbelt
2023-09-11 13:34 ` Darius Rad
2023-09-11 17:28 ` DJ Delorie
2023-09-11 16:17 ` Adhemerval Zanella Netto
2023-09-20 13:36 ` Palmer Dabbelt
2023-09-21 13:47 ` Wang, Yanzhang
2023-10-17 8:28 ` Wang, Yanzhang
2023-10-17 13:42 ` Adhemerval Zanella Netto
2023-10-24 5:59 ` Wang, Yanzhang
2023-10-24 11:39 ` Adhemerval Zanella Netto
2023-10-26 3:30 ` Wang, Yanzhang
2023-08-14 13:12 ` Carlos O'Donell
2023-08-15 1:48 ` Wang, Yanzhang
2023-08-15 1:44 ` [PATCH v2] " yanzhang.wang
2023-12-17 13:16 ` Wang, Yanzhang
2023-12-19 17:44 ` Adhemerval Zanella Netto
2024-01-02 11:02 ` Wang, Yanzhang
2024-01-02 10:54 ` [PATCH v3] " yanzhang.wang
2024-01-02 18:30 ` Adhemerval Zanella Netto
2024-01-17 12:23 ` Andreas Schwab
2024-01-29 12:46 ` Andreas Schwab
2024-02-01 12:39 ` Wang, Yanzhang
2024-02-01 12:53 ` Andreas Schwab
2024-05-21 11:13 ` Maciej W. Rozycki
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=26bd6001-6ff5-dcab-d233-9adb6b8efb6f@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=palmer@dabbelt.com \
--cc=yanzhang.wang@intel.com \
/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).