Re: Crypto++ 5.6.5 and Valgrind

2017-11-28 Thread Jeffrey Walton


On Tuesday, November 28, 2017 at 11:49:17 AM UTC-5, Ingo Naumann wrote:
>
> Dear All, 
>
> I've just upgraded from an older version to Crypto++ 5.6.5 and my 
> Valgrind is seriously unhappy about it. Even the "cryptest.exe v" 
> command crashes with "Illegal instruction" (details on request) when 
> calling it with 
>

Crypto++ 5.6.5 and 6.0 and both Valgrind clean. We disabled a few 
algorithms ASM impl due to Valgrind findings and we are working to 
re-enable them. I'm working on re-enabling some of them right now. See, for 
example, https://stackoverflow.com/q/47533475/608639.

We hit those illegal instructions often during testing. The problem is 
Debian and Fedora provide a Valgrind that is a tad bit old. New processors 
give Valgrind a lot of problems because the VEX decoder can't handle a lot 
of code being generated by GCC 6 and 7.

We work around it by building Valgrind from sources. Its fairly easy once 
you install the packages "automake autoconf libtool". Also see 
http://valgrind.org/downloads/repository.html.

Also note that last time I checked even Valgrind-Git had some missing VEX 
code, but it is not as bad as a distro's version. Usually Fedora catches an 
illegal instruction, but Debian is OK.

Jeff

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Crypto++ 5.6.5 and Valgrind

2017-11-28 Thread Ingo Naumann
Dear All,

I've just upgraded from an older version to Crypto++ 5.6.5 and my
Valgrind is seriously unhappy about it. Even the "cryptest.exe v"
command crashes with "Illegal instruction" (details on request) when
calling it with

valgrind --tool=memcheck --leak-check=full --show-reachable=yes
./cryptest.exe v

as suggested here:

https://www.cryptopp.com/wiki/Profiling

Could anybody confirm or is that just me seeing that?

System is Debian 4.9.0-3-686-pae, gcc (Debian 6.3.0-18) 6.3.0 20170516
in a Virtual Machine (VMWare).

Cheers,

Ingo



-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Please test latest CMake changes

2017-11-28 Thread Marcel Raad
Am 28.11.2017 02:53 schrieb "Jeffrey Walton" :

We added SM3, SM4, Simon and Speck recently. Changes were made to the Cmake
files at https://github.com/noloader/cryptopp-cmake.

Would someone please test them.


Using Visual Studio 2017 on Windows, I get a lot of warnings because
compiler options are passed to the linker. Apart from that, everything
works fine for me on Windows (CMake 3.9.2, MSVC) and Ubuntu Xenial (CMake
3.5, g++).

Marcel

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.