ykk136

Results 5 comments of ykk136

And I confirmed that my AMD CPU does support ssse3.

> Thanks for your comment, I used `lscpu`, and the result is: ![image](https://github.com/variar/klogg/assets/52641693/5ca72ecd-6049-49f7-aec9-bc7c48dc4e4f) Is there any way to solve this build issue?

For the compilation environment, I list all the tools as: 1. gcc / g++: 7.5.0 ![image](https://github.com/variar/klogg/assets/52641693/7c8c371d-b4fc-4361-9819-ce475f951979) ![image](https://github.com/variar/klogg/assets/52641693/b6d0b9da-ed3f-4def-b808-39b10883224e) 2. cmake: 3.20 ![image](https://github.com/variar/klogg/assets/52641693/d6b5c254-bf17-4513-b785-ca3dd0796af8) 3. libboost: 1.65 ![image](https://github.com/variar/klogg/assets/52641693/4cf4e994-295a-4699-bb35-3acc5652291f) 4. Ragel: 6.10 ![image](https://github.com/variar/klogg/assets/52641693/9c7858dc-ab3a-436e-bc18-e4067d0ee8ac) And...

> The build tools are the same as in ubuntu 18.04 docker container. Could you try passing `-DKLOGG_USE_LTO=OFF` to cmake? That should disable link time optimizations, and that is used...

One more question about Generic_CPU flag. What is the difference between `ucm_add_flags(C CXX "-march=x86-64 -mtune=generic")` and `ucm_add_flags(C CXX "-march=native -mtune=generic")`? Will it imapct the final performance of KLogg?