<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Issues using ipp crypto 2018 update 1 with linux gcc in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/Issues-using-ipp-crypto-2018-update-1-with-linux-gcc/m-p/1169221#M26887</link>
    <description>&lt;P&gt;Using the following:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;gcc --version
gcc (Debian 6.3.0-18) 6.3.0 20170516
&lt;/PRE&gt;

&lt;P&gt;Have been able to build and run ipp apps with no problem.&lt;/P&gt;

&lt;P&gt;Using the crypto standalone product, trying to build the ippcp getting started app: &lt;A href="https://software.intel.com/en-us/ipp-crypto-dev-guide-building-intel-ipp-cryptography-applications"&gt;https://software.intel.com/en-us/ipp-crypto-dev-guide-building-intel-ipp-cryptography-applications&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;command line:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;gcc -I /opt/intel/ippcp/include -L /opt/intel/ippcp/lib/intel64 -lippcp -o testippcp ippcp.cc&lt;/PRE&gt;

&lt;P&gt;Results in in segmentation fault. Please advise.&lt;/P&gt;

&lt;P&gt;Gdb:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;$ gdb ./testippcp 
...
(gdb) run
Starting program: /home/mike/src/ipptest/testippcp 

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7de886a in call_init (l=0x2020800, argc=argc@entry=1, argv=argv@entry=0x7fffffffe108, 
    env=env@entry=0x7fffffffe118) at dl-init.c:58
58	dl-init.c: No such file or directory.
&lt;/PRE&gt;

&lt;P&gt;Strace:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;$ strace ./testippcp
...
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb18f6e1000
arch_prctl(ARCH_SET_FS, 0x7fb18f6e1b40) = 0
mprotect(0x7fb18f2b0000, 16384, PROT_READ) = 0
mprotect(0x7fb18ed0d000, 4096, PROT_READ) = 0
mprotect(0x7fb18ef15000, 4096, PROT_READ) = 0
mprotect(0x7fb18f4d1000, 4096, PROT_READ) = 0
mprotect(0x55661e4bb000, 4096, PROT_READ) = 0
mprotect(0x7fb18f6fe000, 4096, PROT_READ) = 0
munmap(0x7fb18f6e3000, 107741)          = 0
brk(NULL)                               = 0x55661f0d1000
brk(0x55661f0f2000)                     = 0x55661f0f2000
open("/opt/intel/ippcp/lib/intel64/libippcpe9.so", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0&amp;gt;\0\1\0\0\0`\272\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=2161405, ...}) = 0
mmap(NULL, 4118064, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb18e61b000
mprotect(0x7fb18e805000, 2097152, PROT_NONE) = 0
mmap(0x7fb18ea05000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1ea000) = 0x7fb18ea05000
close(3)                                = 0
mprotect(0x7fb18ea05000, 4096, PROT_READ) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x1020908} ---
+++ killed by SIGSEGV +++
Segmentation fault
&lt;/PRE&gt;

&lt;P&gt;&amp;nbsp;
	&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 07 Dec 2017 01:03:05 GMT</pubDate>
    <dc:creator>wilson__mike</dc:creator>
    <dc:date>2017-12-07T01:03:05Z</dc:date>
    <item>
      <title>Issues using ipp crypto 2018 update 1 with linux gcc</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Issues-using-ipp-crypto-2018-update-1-with-linux-gcc/m-p/1169221#M26887</link>
      <description>&lt;P&gt;Using the following:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;gcc --version
gcc (Debian 6.3.0-18) 6.3.0 20170516
&lt;/PRE&gt;

&lt;P&gt;Have been able to build and run ipp apps with no problem.&lt;/P&gt;

&lt;P&gt;Using the crypto standalone product, trying to build the ippcp getting started app: &lt;A href="https://software.intel.com/en-us/ipp-crypto-dev-guide-building-intel-ipp-cryptography-applications"&gt;https://software.intel.com/en-us/ipp-crypto-dev-guide-building-intel-ipp-cryptography-applications&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;command line:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;gcc -I /opt/intel/ippcp/include -L /opt/intel/ippcp/lib/intel64 -lippcp -o testippcp ippcp.cc&lt;/PRE&gt;

&lt;P&gt;Results in in segmentation fault. Please advise.&lt;/P&gt;

&lt;P&gt;Gdb:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;$ gdb ./testippcp 
...
(gdb) run
Starting program: /home/mike/src/ipptest/testippcp 

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7de886a in call_init (l=0x2020800, argc=argc@entry=1, argv=argv@entry=0x7fffffffe108, 
    env=env@entry=0x7fffffffe118) at dl-init.c:58
58	dl-init.c: No such file or directory.
&lt;/PRE&gt;

&lt;P&gt;Strace:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;$ strace ./testippcp
...
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb18f6e1000
arch_prctl(ARCH_SET_FS, 0x7fb18f6e1b40) = 0
mprotect(0x7fb18f2b0000, 16384, PROT_READ) = 0
mprotect(0x7fb18ed0d000, 4096, PROT_READ) = 0
mprotect(0x7fb18ef15000, 4096, PROT_READ) = 0
mprotect(0x7fb18f4d1000, 4096, PROT_READ) = 0
mprotect(0x55661e4bb000, 4096, PROT_READ) = 0
mprotect(0x7fb18f6fe000, 4096, PROT_READ) = 0
munmap(0x7fb18f6e3000, 107741)          = 0
brk(NULL)                               = 0x55661f0d1000
brk(0x55661f0f2000)                     = 0x55661f0f2000
open("/opt/intel/ippcp/lib/intel64/libippcpe9.so", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0&amp;gt;\0\1\0\0\0`\272\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=2161405, ...}) = 0
mmap(NULL, 4118064, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb18e61b000
mprotect(0x7fb18e805000, 2097152, PROT_NONE) = 0
mmap(0x7fb18ea05000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1ea000) = 0x7fb18ea05000
close(3)                                = 0
mprotect(0x7fb18ea05000, 4096, PROT_READ) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x1020908} ---
+++ killed by SIGSEGV +++
Segmentation fault
&lt;/PRE&gt;

&lt;P&gt;&amp;nbsp;
	&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2017 01:03:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Issues-using-ipp-crypto-2018-update-1-with-linux-gcc/m-p/1169221#M26887</guid>
      <dc:creator>wilson__mike</dc:creator>
      <dc:date>2017-12-07T01:03:05Z</dc:date>
    </item>
    <item>
      <title>HI, Mike, </title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Issues-using-ipp-crypto-2018-update-1-with-linux-gcc/m-p/1169222#M26888</link>
      <description>&lt;P&gt;HI, Mike,&amp;nbsp;&lt;BR /&gt;
	What's your processor in your test system?&amp;nbsp;&lt;BR /&gt;
	&lt;BR /&gt;
	Regards,&lt;BR /&gt;
	Chao&lt;/P&gt;</description>
      <pubDate>Fri, 08 Dec 2017 11:58:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Issues-using-ipp-crypto-2018-update-1-with-linux-gcc/m-p/1169222#M26888</guid>
      <dc:creator>Chao_Y_Intel</dc:creator>
      <dc:date>2017-12-08T11:58:44Z</dc:date>
    </item>
    <item>
      <title>Hi Chao, using AMD FX(tm)</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Issues-using-ipp-crypto-2018-update-1-with-linux-gcc/m-p/1169223#M26889</link>
      <description>&lt;P&gt;Hi Chao, using AMD FX(tm)-4300 Quad-Core Processor&lt;/P&gt;

&lt;P&gt;Don't worry I this is just a test system, we use only genuine Intel for production :)&lt;/P&gt;

&lt;P&gt;The IPP 2018 update 1 seems to be compatible with this processor. Also earlier versions of IPP + crypto have worked.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;

&lt;P&gt;--Mike&lt;/P&gt;</description>
      <pubDate>Fri, 08 Dec 2017 20:39:08 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Issues-using-ipp-crypto-2018-update-1-with-linux-gcc/m-p/1169223#M26889</guid>
      <dc:creator>wilson__mike</dc:creator>
      <dc:date>2017-12-08T20:39:08Z</dc:date>
    </item>
    <item>
      <title>thanks, Mike.  We will have</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Issues-using-ipp-crypto-2018-update-1-with-linux-gcc/m-p/1169224#M26890</link>
      <description>&lt;P&gt;thanks, Mike.&amp;nbsp; We will have some further check on this.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Dec 2017 05:52:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Issues-using-ipp-crypto-2018-update-1-with-linux-gcc/m-p/1169224#M26890</guid>
      <dc:creator>Chao_Y_Intel</dc:creator>
      <dc:date>2017-12-11T05:52:01Z</dc:date>
    </item>
  </channel>
</rss>

