On 21/06/26 05:10, H.J. Lu wrote: > On Sun, Jun 21, 2026 at 3:33 PM <[email protected]> wrote: >> >> Dear contributor, >> >> Our automatic CI has detected problems related to your patch(es). Please >> find some details below. >> >> In glibc_check master-arm, after: >> | commit glibc-2.43.9000-439-g53d909a283 >> | Author: H.J. Lu <[email protected]> >> | Date: Mon Apr 13 08:23:05 2026 +0800 >> | >> | elf: Support THP segment load with madvise enabled THP >> | >> | The current THP segment load approach works only when THP is enabled >> | with always in the kernel. If THP is enabled with madvise in the >> | kernel, to enable THP segment load in an application, madvise should >> | ... 43 lines of the commit log omitted. >> >> Produces 2 regressions: >> | >> | regressions.sum: >> | Running glibc:elf ... >> | FAIL: elf/tst-thp-1-no-s-code-static >> | FAIL: elf/tst-thp-1-static >> > > There are > > ifeq (yes,$(enable-static-pie)) > # These static PIE tests fail on arm due to limitations of arm32 kABI: > # https://sourceware.org/bugzilla/show_bug.cgi?id=34096 > test-xfail-tst-thp-1-no-s-code-static = yes > test-xfail-tst-thp-1-static = yes > endif > > Since they should be built with -Wl,-Ttext-segment=$(THP-PAGE-SIZE) > why do they fail on arm? >
It is most likely because static-pie support on armhf was just recently enabled on glibc, and not enabled by default on released gcc (as a side note, I will need to check if Sam has enabled on it). I think we will should either to just build them for enable-static-pie or XFAIL the on arm regardless of enable-static-pie. _______________________________________________ linaro-toolchain mailing list -- [email protected] To unsubscribe send an email to [email protected]
