Some build configurations for gcc on Sparc use the outdated gcc switch -mv8.
The switch was deprecated at least back for gcc 2.95.2 in October 1999
([1][2]). GCC 4 does no longer support the -mv8 switch but instead now
you have to use the switch that was already preferred for version
2.95.2:
More coming in.
Here are preliminary results for 32- and 64-bit ARM. Preliminary means
that they are incomplete and subject to change. But in a sense they
underpin some of the points in previous post, both in message itself and
source code commentary.
Consider 32-bit results. First column is
On Sun, May 24, 2015, Dixon Xavier wrote:
Hi,
Going by the description in links:
http://openssl.6102.n7.nabble.com/FIPS-Module-1-2-build-with-Visual-Studio-2010-fails-self-tests-td36372.html
Hi,
Going by the description in links:
http://openssl.6102.n7.nabble.com/FIPS-Module-1-2-build-with-Visual-Studio-2010-fails-self-tests-td36372.html
http://mailing.openssl.dev.narkive.com/HfYeReuA/fips-module-1-2-build-with-visual-studio-2010-fails-self-tests
I understand that adding /fixed flag
Hello,
I want to add OpenSSL to my Cortex M3 bare metal platform. I am using a Keil
IDE and I am having trouble configuring a library to support this
environment. Any suggestions would be most appreciated.
Thanks for your time!
Best regards
Will
Changing the movzwl to movzbl in bn_get_bits5 eliminates the valgrind
error. But this isn't a valid fix since bn_get_bits5 no longer returns
the correct data. My assembly skills are near nil. Maybe someone else
can propose a valid fix.
Having said this, this does show the problem appears
I don't think its optimizing it out I agree with you, but your
suggested change resolved the error so Wim was right about it being
undefined behaviour, and the tool which uses clang 3.4 was warning us
about that.
I added my own debugging statement and ran ectest and it is indeed
undefined
I ran some more tests, the issue seems to be optimization not platform
types...
If non-matching platform config happens to work, it's a party trick, not
support matter.
when I removed -xO[n] from CFLAG, something (either cc or openssl compile set
up) turned back on optimization at -xO3
Hi Andy,
Thank you for your reply! I am CC'ing Lei on mine.
On Wed, May 20, 2015 at 12:55:10PM +0200, Andy Polyakov via RT wrote:
For reference. icc was not cared for for quite some time. Initially it
was possible for me, by then university employee, to use it, but then
they changes terms