On Tue, 19 Sep 2017, Andreas Schwab wrote: > On Sep 18 2017, Joseph Myers <jos...@codesourcery.com> wrote: > > > Building glibc for many different configurations and running the > > compilation parts of the testsuite runs into failures of the > > elf/check-execstack test for hppa, ia64 and microblaze. > > ia64 is non-execstack by default, so it doesn't need any marking. The > same is true for every architecture that doesn't override > elf_read_implies_exec, which includes microblaze and hppa.
Thanks for the explanation. I've sent a glibc patch <https://sourceware.org/ml/libc-alpha/2017-09/msg00734.html>. I think the key questions for architecture experts now are: on each of those three architectures, do trampolines ever require executable stacks, and, if they do, how does this work at present when the kernel defaults to non-executable and my understanding at <https://sourceware.org/ml/libc-alpha/2017-09/msg00747.html> would be that glibc would only make thread stacks executable on those architectures, not the main process stacks, and GCC will never generate an explicit marker on those architectures to request an executable stack? -- Joseph S. Myers jos...@codesourcery.com
