On Wed, 25 Jul 2018, Vineet Gupta wrote: > Chiming in as I'm looking into these things myself in context of testing > for ARC port submission. Do we really need to fix this part - in this > way. I'd vote to not force the execstack through linker and rely on gcc > generating this itself when it knows it doing something for trampolines. > And only if target gcc doesn't support it (detected via configure test) > should this be done. The whole point of this test is to verify executable stack changes on dlopen of a module requiring an executable stack. Thus, for this test to work correctly, this module must be forced to have a marking as needing an executable stack. -- Joseph S. Myers joseph at codesourcery.com
