<div>Sverker
</div><div><br></div><div>Many thanks for the response. The code module agrees, at least on the two systems I have to hand (OSX and CentOS)</div><div><div><br></div><div></div></div><blockquote type="cite"><div><div>Erlang R16B03 (erts-5.10.4) [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]</div><div><br></div><div>Eshell V5.10.4 (abort with ^G)</div><div>1> code:is_module_native(lists).</div><div>false</div></div>
<div><div></div></div></blockquote><div><div><br></div><div>When we were compiling the modules by hand we certainly saw native in the module:info() response, but the code:is_module_native() call is a much cleaner way to tell!</div><div><br></div><div>Kind regards</div><div><br></div><div>Adrian</div><div><br></div><div>-- </div><div>Adrian Roe</div><div>Sent with <a href="http://www.sparrowmailapp.com/?sig">Sparrow</a></div><div><br></div></div>
<p style="color: #A0A0A8;">On Wednesday, 2 April 2014 at 19:27, Sverker Eriksson wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div>What does code:is_module_native(lists)
say?<br>
<br>
/Sverker<br>
<br>
<br>
On 04/02/2014 08:11 PM, Adrian Roe wrote:<br>
</div><blockquote type="cite"><div>
<pre wrap="">We’ve been using Erlang in production for quite a few years now and for the first time we have a project that really benefits from HIPE / native code being turned on (before things have always been fast enough without and the benefit of more detailed stack traces etc outweighed any performance gains). We did some benchmarking by compiling single modules with HIPE - both in our application code and then going through key OTP / Erlang library modules, clearing sticky_directory errors and recompiling them one by one with +native.
Now that it is clear that (for this use case) native / HIPE is the way to go, I went to the project’s build box and recompiled Erlang (R16B03) from source with
./configure --enable-hipe --enable-native-libs
in the expectation that all libraries would be compiled with +native
Checking (for example) lists.beam gives:
</pre><blockquote type="cite"><div>
<pre wrap="">Erlang R16B03 (erts-5.10.4) [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]
Eshell V5.10.4 (abort with ^G)
1> lists:module_info().
[{exports,[{append,2},
{append,1},
{subtract,2},
{nth,2},
{nthtail,2},
{prefix,2},
{suffix,2},
{last,1},
{seq,2},
{seq,3},
{sum,1},
{duplicate,2},
{min,1},
{max,1},
{sublist,3},
{sublist,2},
{zip,2},
{zip3,3},
{unzip3,1},
{zipwith,3},
{zipwith3,4},
{merge,1},
{merge3,3},
{rmerge3,3},
{merge,...},
{...}|...]},
{imports,[]},
{attributes,[{vsn,[329984570326751442388870353176450263952]}]},
{compile,[{options,[{outdir,"/net/isildur/ldisk/daily_build/r16b03_prebuild_opu_o.2013-12-09_20/otp_src_R16B03/lib/stdlib/src/../ebin"},
{i,"/net/isildur/ldisk/daily_build/r16b03_prebuild_opu_o.2013-12-09_20/otp_src_R16B03/lib/stdlib/src/../include"},
{i,"/net/isildur/ldisk/daily_build/r16b03_prebuild_opu_o.2013-12-09_20/otp_src_R16B03/lib/stdlib/src/../../kernel/include"},
warnings_as_errors,debug_info]},
{version,"4.9.3"},
{time,{2013,12,9,19,26,33}},
{source,"/net/isildur/ldisk/daily_build/r16b03_prebuild_opu_o.2013-12-09_20/otp_src_R16B03/lib/stdlib/src/lists.erl"}]}]
</pre>
</div></blockquote><pre wrap="">No sign of native anywhere…
I’ve tried this on OSX, CentOS and Ubuntu all with the same result, so it’s clearly me doing something stupid, but I can’t see it.
I obviously could go through and rebuild each module in turn (as we did for the benchmarking) but it doesn’t feel like the right way forward.
Any suggestions gratefully received!
Kind regards
Adrian
--
Dr Adrian Roe
Director
</pre>
<br>
<fieldset></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</div></blockquote><br>
</div></div></span>
</blockquote>
<div>
<br>
</div>