| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
* maint:
mnesia: Fix error handling in abort write
|
|
* dgud/mnesia/backup-error-handling/OTP-14776:
mnesia: Fix error handling in abort write
|
|
|
|
Only change is doc.
|
|
|
|
add hibernate_after to the gen options type spec
|
|
* maint:
debugger: Do not quote variables and button names in windows
|
|
* hasse/debugger/fix_unicode/OTP-14802:
debugger: Do not quote variables and button names in windows
|
|
v3_kernel could generate a #k_break{} with only one variable, even if
the preceding code and succeding code expected more than one value. It
happened to work anyway because the value returned from the break was
not actually used.
|
|
We used to not care about the number of values returned from the
'after infinity' clause in a receive (because it could never be
executed). It is time to start caring because this will cause problem
when we will soon start to do some more aggressive optimizizations.
|
|
* maint:
fix output formatting in several HiPE debug BIFs
|
|
fix output formatting in several HiPE debug BIFs
OTP-14804
|
|
|
|
* bjorn/compiler/clean-up-codegen:
bs_match_SUITE: Cover more clauses in v3_codegen:bs_rename_ctx/4
Clean up and comment code generation for basic blocks
Stop trying to maximize the use of x(0)
Clean up collection of basic blocks
|
|
|
|
|
|
|
|
System resources/functionality may need to be reference counted
to be handled correctly when used or enabled/disabled from more
than one process or application.
It is easier to handle this in erlang code than in erts, so make a
process that deals with the housekeeping.
|
|
The bug was introduced in commit 7eaaf5.
|
|
* maint:
crypto: engine_SUITE update
crypto: fix pubkey_to_privkey
|
|
* hans/crypto/fix_wrong_error_return_privkey_to_pubkey:
crypto: engine_SUITE update
crypto: fix pubkey_to_privkey
|
|
* maint:
public_key: Separated failing gen_ec_param test case into two because two different curve classes were tested in one TC and on one test machine only one was supported
|
|
* hans/public_key/cuddle_tests:
public_key: Separated failing gen_ec_param test case into two because two different curve classes were tested in one TC and on one test machine only one was supported
|
|
because two different curve classes were tested in one TC and on one test machine only one was supported
|
|
|
|
|
|
|
|
* lars/crypto/valgrind-fixes/OTP-14800:
[crypto] Fix memory leak
|
|
Fix memory leak in engine load code found by valgrind.
|
|
|
|
* ingela/ssl/timing:
ssl: Align timing just in case
|
|
* peterdmv/inets/fix-httpc/OTP-14799:
inets: Fix httpc path handling
|
|
OTP-14256
OTP-14797
|
|
* maint:
Clarification in doc of unicode:characters_to_list/2
|
|
* rickard/unicode-doc/ERL-516/OTP-14798:
Clarification in doc of unicode:characters_to_list/2
|
|
|
|
|
|
|
|
|
|
The option no longer does anything; systems that lack support for
non-blocking sendfile(2) will use the Erlang fallback.
|
|
The parts relating to drivers/ports are now obsolete, and the
provided example was far noisier than it had to be; the only
relevant metric is the number of calls and it's up to the user to
decide how those will be reduced. One could argue for its complete
removal, but I'm inclined to leave it be.
|
|
|
|
efile_drv is gone and so is the need for file-specific DTrace. The
new implementation works fine with the normal tracing mechanism so
there's nothing preventing anyone from making an erl_tracer nif
that forward these events to DTrace.
|
|
The option no longer does anything at all.
|
|
|
|
There doesn't seem to be any science behind the long delays, and
the (newly introduced) dry run forces us to eat them twice, so
they've been shortened to more reasonable values.
|
|
Code loading is done through dirty IO now, causing the
dirty_scheduler_exit tests to fail as they block their own progress
by invoking erts_debug:dirty_io(wait, _); the spawned processes
will exit normally before we have a chance to kill them.
To get around this, we perform a dry run to ensure that all required
code is loaded. It isn't particularly pretty (or fast) but it saves
us the hassle of maintaining a module list (cf. embedded mode).
|
|
The old driver didn't fall back to using write(2) if writev(2) failed
due to the combined length of the iov overflowing a ssize_t, but the
new one doesn't have any problems with it so we failed this test with
a case_clause error on 32-bit machines.
|
