Age | Commit message (Collapse) | Author |
|
This is achieved by filtering perlasm output through arm-xlate.pl. But note
that it's done only if "flavour" argument is not 'void'. As 'void' is
default value for other ARM targets, permasm output is not actually
filtered on previously validated platforms.
Reviewed-by: Dr. Stephen Henson <steve@openssl.org>
|
|
Reviewed-by: Dr. Stephen Henson <steve@openssl.org>
|
|
(cherry picked from commit 1a9d60d2e3b02d5e1954fc71c92bf3a6af691495)
|
|
|
|
|
|
|
|
|
|
Other Intel processors +5%, Opteron -2%.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
for more details.
|
|
|
|
|
|
|
|
update commentary...
|
|
ABI and binutils.
|
|
|
|
PR: 2335
|
|
|
|
|
|
|
|
|
|
Modest improvement coefficients mean that code already had some
parallelism and there was not very much room for improvement. Special
thanks to Ted Krovetz for benchmarking the code with such patience.
|
|
|
|
ARM assembler modules.
|
|
opcodes detected in executable segment" error.
|
|
be done, it's definitely not the way to do it. So far answer to the
question was to ./config -Wa,--noexecstack (adopted by RedHat).
|
|
|
|
|
|
I can't think of any other cause for failure
|
|
|
|
|
|
|
|
|
|
forgotten CPUs.
|
|
|
|
|
|
|
|
make it Purify-friendly...
|
|
|
|
|
|
|
|
|