topic Execstack on Linux intel64 libraries in Intel® Integrated Performance Primitives

Execstack on Linux intel64 libraries

Maarten_Hoeben1 — Wed, 04 Apr 2012 11:04:15 GMT

Hi,

We found that the execstack flag is set for the intel64shared library binaries. We find this generally undesirable, although we understand that for some optimizations executing from the local stack may be required to get the most out of the platform, we would like to know how to work around requiring our application to inherit this. Are there libraries available that do not require execstack? Is there an overview of which functions require execstack?

Thanks in advance for the response.

Maarten Hoeben

Execstack on Linux intel64 libraries

Ying_H_Intel — Fri, 08 Jun 2012 03:12:32 GMT

Hi Maarten,

The Intel 64 shared library, do you mean the IPP 7.0.6 or IPP 7.0.7 for linux, right?

And your question have been escalated to IPP developer. Hope get back to you soon.

Regards,
Ying

Execstack on Linux intel64 libraries

Ying_H_Intel — Wed, 13 Jun 2012 08:02:35 GMT

Hi Maarten,

Our developer investigated the problem and verified we dont set the flag for shared libraries. So haven't idea about what we can do here.

Regards,
Ying

The problem is likely one or

Tom_Truscott — Fri, 24 May 2013 19:19:47 GMT

The problem is likely one or more assembler (.s) files that lack the following line, which icc/icpc/... puts at the end of the assembler output:

.section .note.GNU-stack,"",@progbits

This indicates that the .s code does not need an executable stack. The linux linker default is to mark its output "execstack" unless *all* the objectsin the link have this note.

(The MKL library has many 100s of machine-generated .s files that neglect this detail.)