* ci notify: > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's > #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on > the usual project channel. > > We understand that it might be difficult to find the necessary logs or > reproduce the issue locally. If you can't get what you need from our CI > within minutes, let us know and we will be happy to help. > > In glibc_check master-arm after: > > | 29 patches in glibc > | Patchwork URL: https://patchwork.sourceware.org/patch/98131 > | 59fbaae3a6e Optimize various ways to obtain the page size using > <bits/pagesize.h> > | 564bcbe0067 posix: Use <support/next_to_fault.h> in tst-fnmatch3 > | 27a360de01d malloc: Use volatile as compiler barrier in tst-memalign, > tst-valloc > | e24dfc8d9a8 Linux: Optimize getpagesize using <sys/pagesize.h> > | 3283915ffd0 Install the <sys/pagesize.h> header file > | ... and 24 more patches in glibc > | ... applied on top of baseline commit: > | 6948ee4edf0 stdio-common: Fix memory leak in tst-freopen4* tests on > UNSUPPORTED > > FAIL: 1 regressions > > regressions.sum: > | === glibc tests === > | > | Running glibc:elf ... > | XPASS: elf/tst-load-alignment
Does this mean that the 32-bit arm tester uses a non-default toolchain that increases page alignment to 64 KiB? With my cross-tester, elf/tst-load-alignment fails as expected because the binaries can only be loaded on 4 KiB page systems, based on the program header layout. Thanks, Florian _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
