Age | Commit message (Collapse) | Author |
|
Compiling this example takes less than a second for OTP 21:
-define(B, {?A,?A,?A,?A,?A}).
-define(C, {?B,?B,?B,?B,?B}).
-define(D, {?C,?C,?C,?C,?C}).
-define(E, {?D,?D,?D}).
f() -> ?E = foo:bar().
The compilation time for OTP 22 is about 10 seconds. Most of the
time is spent in `beam_ssa_dead`.
This commit introduces several optimizations to bring the compilation
time down to about a second.
The most important of those optimizations is limiting the effort spent
searching forward for a joining point for the success and failure
labels for a two-way branch. This change is helped by the change of
representation of variable sets from `ordsets` to `cerl_sets`.
https://bugs.erlang.org/browse/ERL-1014
|
|
|
|
* ingela/ssl/test-enhancment:
ssl: Extend tests
ssl: Fix better OpenSSL support in test framework
ssl: Avoid broken ALPN/NPN renegotiation in OpenSSL
|
|
|
|
|
|
All these test work fine with current OpenSSL master
|
|
* hans/ssh/early_crash_fail_logging/ERL-990/OTP-15962:
ssh: added log/4
ssh: Fix log problem in early stages of initialization
ssh: Fix potential crash if failure in init of client
|
|
|
|
maint
|
|
|
|
|
|
|
|
|
|
|
|
Make even deprecated test cases use the tc_try function (so that
all test cases look the same). Also make the skip reason for those
test cases be slightly more readable.
|
|
Make use of the tc_try function(s) in all "active" test cases.
|
|
Add a utility function, tc_try/2,3, for running test cases
in a uniform way.
|
|
Add a sleep to reduce the chance that process exit
has not been "processed" by the nif code.
Also increased the test case timetrap for the
sc_ctrl_proc_exit group of test cases.
OTP-15904
|
|
* ingela/ssl/test-enhancment:
ssl: Remove NPN test from DTLS interop tests
|
|
OpenSSL does note seem to support NPN for DTLS so
we will have to skip those test
|
|
* peterdmv/ssl/test-improvements:
ssl: Enable TLS 1.3 test groups in FT
|
|
|
|
* peterdmv/ssl/psk:
ssl: Reorder testcases in ssl_api_SUITE
ssl: Fix handshake pause in TLS 1.3
ssl: Implement option honor_cipher_order in TLS 1.3
ssl: Add test for option supported_groups
ssl: Document option supported_groups
ssl: Fix ssl_api_SUITE:connection_information
ssl: Fix property tests for SSLv3
ssl: Update property tests with pre_shared_key
ssl: Implement pre_shared_key extension
ssl: Update property tests with psk_key_exchange_modes
ssl: Implement psk_key_exchange_modes extension
|
|
* ingela/ssl/test-enhancment:
ssl: Move reuseaddr test to tls_api_SUITE
ssl: Avoid devision with zero in ssl_bench_SUITE
|
|
|
|
When one test in ssl_bench_SUITE is run as a
smoke test in the ordinary test runs it might get
problems on windows as time measurement is to coarse
|
|
|
|
|
|
|
|
|
|
|
|
This commit fixes the connection_information testcase with TLS 1.3
connections.
|
|
|
|
|
|
Implement encode/decode of pre_shared_key.
|
|
|
|
Implement encode/decode of psk_key_exchange_modes.
|
|
* ingela/ssl/correct-test-groups:
ssl: Correct groups
|
|
|
|
* ingela/ssl/continue-restructure-tests:
ssl: Avoid race in test code
ssl: Remove duplicate suite
ssl: Continue moving test form basic_SUITE to more appropriate suites
ssl: Add ssl_socket_SUITE
|
|
|
|
The suite was renamed tls_1_3_versions_SUITE but
apparently not via git, so the old file remained.
|
|
|
|
|
|
* ingela/ssl/sane-openssl:
ssl: Old OpenSSL implementation does not ignore trailing client hello data
|
|
Rename some of the structures and callback functions
(socket -> esock).
OTP-15955
|
|
Renamed constants (defines): SOCKET_ -> ESOCK_
OTP-15955
|
|
The naming "convention" for "top" functions of the esock
nif module was: The API functions where called nif_<foo>
This function did basic checks and arg extraction and then
called the a function called n<foo>, which was the one doing
the actual work.
Unfortunately, och some platforms (AIX) these second names,
n<foo>, clashed with system functions.
So, in order to avoid this, the naming of second function
has been changed to esock_<foo>.
OTP-15955
|
|
Removed unnecessary spec's causing dialyzer warnings.
|
|
Do not test TLS 1.0 with these old versions as we do send hello extensions
for those implementations that will use them, and trailing unknown data
should be ignored by RFC complient implementations.
|