[CP2K-user] libxsmm target

[Grzegorz Wieczorek]

Hi! Thank you for the explanation.
Best,
g

On Sunday, December 27, 2020 at 9:33:09 AM UTC+1 h... at gmail.com wrote:

> Hello,
>
> thank you for posting into CP2K forum!  Indeed, INTRINSICS=1 overcomes 
> build issues on systems with outdated Binutils. CP2K toolchain installs GCC 
> from scratch but omits GNU Binutils. In case of CP2K's usage, there is no 
> harm from INTRINSICS=1 (affected functionality is not used in CP2K). 
> Further, the next release of LIBXSMM reimplemented matrix-element-wise 
> functionality which was mostly affected by the INTRINSIC setting. In turn,  
> matrix-element-wise functionality is mainly present in LIBXSMM's 
> Deeplearning Domain (CP2K only uses the SMM domain). I will likely remove 
> this warning in an upcoming release of LIBXSMM.
>
> Best wishes,
> H.
>
> wiec... at gmail.com schrieb am Samstag, 26. Dezember 2020 um 23:57:04 
> UTC+1:
>
>> Hello,
>> The tools/toolchain/scripts/install_libxsmm.sh compiles the library with 
>> INTRINSICS=1 without further specifying the target processor (cp2k 8.0 
>> dev). The result is the library optimized for sse4.2. The make.log says:
>>
>>
>> --------------------------------------------------------------------------------
>>
>> INTRINSICS=1 without setting AVX can reduce performance of certain code 
>> paths.
>>
>> If adjusting INTRINSICS was necessary, reconsider an updated tool chain.
>>
>>
>> --------------------------------------------------------------------------------
>> Is there a particular reason for such setting? What about just AVX=2, or 
>> even TARGET="-march=native mtune=native"?
>> Thank you for cp2k!!
>> Best,
>> g
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cp2k.org/archives/cp2k-user/attachments/20201227/554dca8f/attachment.htm>