Hi, 

May I know your environments? (Linux? Emscripten version?), I would like to 
see if I can reproduce your situation.

On Wednesday, April 8, 2015 at 11:41:16 PM UTC+8, [email protected] 
wrote:
>
> Hi everybody: 
>
> I am trying to compile kakukogou emscripten (
> https://github.com/kakukogou/opencv/tree/opencvjs 
> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fkakukogou%2Fopencv%2Ftree%2Fopencvjs&sa=D&sntz=1&usg=AFQjCNFXL4Z5ZpMYhoZc_6NjoKsEBZjdkg>)
>   opencv 
> library and it compiles fine except these warnings.
>
> WARNING  root: ignoring dynamic library libopencv_core.so.3.0.0 because 
> not compiling to JS or HTML, remember to link it when compiling to JS or 
> HTML at the end
> WARNING  root: ignoring dynamic library libopencv_imgproc.so.3.0.0 because 
> not compiling to JS or HTML, remember to link it when compiling to JS or 
> HTML at the end
> (there are more warnings with the same type, but I write a few).
>
> I think this is emscripten issue because there is no any output to js or 
> html output.
>
> *But the problem, is when I try to link opencv libraries in facedetection 
> example, I get this error: *
>
> *fUse:   %umul9 = tail call { i16, i1 } @llvm.umul.with.overflow.i16(i16 
> %61, i16 %59)*
> *LLVM ERROR: ExpandArithWithOverflow: At least one argument of 
> *.with.overflow must be a constant*
> *Traceback (most recent call last):*
> *  File 
> "/home/VICOMTECH/uelordi/SDK/emsdk_portable/emscripten/master/emcc", line 
> 1301, in <module>*
> *    shared.Building.llvm_opt(final, link_opts)*
> *  File 
> "/home/VICOMTECH/uelordi/SDK/emsdk_portable/emscripten/master/tools/shared.py",
>  
> line 1461, in llvm_opt*
> *    assert os.path.exists(target), 'Failed to run llvm optimizations: ' + 
> output*
> *AssertionError: Failed to run llvm optimizations:*
>
> My script is, the same which is in faceDetection example, and I 
> add --llvm-opts 0 option,  because it seems a clang optimization problem, 
> but I have the same error. 
>
> Thanks in advance. 
>
>
>
> El miércoles, 31 de diciembre de 2014, 7:51:22 (UTC+1), Tzu-Hao Kuo (Kaku) 
> escribió:
>>
>> HI,
>>
>> I recently evaluate the performance of OpenCV with asm.js. 
>> Thanks to the OpenCV team, there are already lots of performance tests in 
>> each OpenCV module. 
>> What I have done is that compile OpenCV library and its performance tests 
>> both in native and with asm.js. 
>> Run the native performance test and the javascript performance test (with 
>> the Firefox javascript engine). 
>> And the statistics data could be found in the following Google Sheet 
>> link:https://docs.google.com/spreadsheets/d/1w8gr1_q_dQclTaGyiMtAhlwj_5_HPVKbHWfwUszPU40/edit?usp=sharing
>>
>> In summary, there are about 20% tests are faster or equal to the native 
>> performance and about 60% tests are faster than 3x native performance.
>>
>> Some patterns are observed. 
>> First, tests with operations which convert floating point values into 
>> integer values are much slower. 
>> Second, in native environment, single operation is much faster when it is 
>> dealing with integer type data comparing to dealing with floating point 
>> values; 
>> however, in javascript environment, the same operation performs equally in 
>> each data type, which leads to relatively larger performance drop in 
>> non-floating point data type.
>>
>>
>> By traversing old posts, I found several people have tried to use OpenCV 
>> in their own projects, however, there is few performance information.
>> I post this message here is intending to open a discussion forum which 
>> could collect information about OpenCV with asm.js and especially the 
>> performance.
>> This message is also posted as a discussion bug in Mozilla Bugzilla, the 
>> link is, https://bugzilla.mozilla.org/show_bug.cgi?id=1116674.
>>
>> Tzuhao
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to