Commit 0a2101e52b for openssl.org
commit 0a2101e52b9257044b2c6251718da34b0db3b5b2
Author: Eugene Syromiatnikov <esyr@openssl.org>
Date: Sat Apr 11 12:16:05 2026 +0200
NOTES-NONSTOP.md: remove the "Linking and Loading Considerations" section
Since the atexit() handler setup was removed in [1], the section content
is no longer relevant; remove it.
[1] https://github.com/openssl/openssl/pull/29385
References: https://github.com/openssl/openssl/issues/30742
Signed-off-by: Eugene Syromiatnikov <esyr@openssl.org>
Reviewed-by: Nikola Pajkovsky <nikolap@openssl.org>
Reviewed-by: Saša NedvÄ›dický <sashan@openssl.org>
MergeDate: Tue Apr 14 08:50:36 2026
(Merged from https://github.com/openssl/openssl/pull/30776)
diff --git a/NOTES-NONSTOP.md b/NOTES-NONSTOP.md
index bddae7675d..b41758da20 100644
--- a/NOTES-NONSTOP.md
+++ b/NOTES-NONSTOP.md
@@ -55,26 +55,6 @@ option to `./Configure`.
TNS/E has moved to a limited support state, so fixes for this platform will not
be guaranteed in future.
-Linking and Loading Considerations
-----------------------------------
-
-Because of how the NonStop Common Runtime Environment (CRE) works, there are
-restrictions on how programs can link and load with OpenSSL libraries.
-On current NonStop platforms, programs cannot both statically link OpenSSL
-libraries and dynamically load OpenSSL shared libraries concurrently. If this
-is done, there is a high probability of encountering a SIGSEGV condition
-relating to `atexit()` processing when a shared library is unloaded and when
-the program terminates. This limitation applies to all OpenSSL shared library
-components.
-
-A control has been added as of 3.3.x to disable calls to `atexit()` within the
-`libcrypto` builds (specifically in `crypto/init.c`). This switch can be
-controlled using `disable-atexit` or `enable-atexit`, and is disabled by default
-for NonStop builds. If you need to have `atexit()` functionality, set
-`enabled-atexit` when configuring OpenSSL to enable the `atexit()` call to
-register `OPENSSL_cleanup()` automatically. Preferably, you can explicitly call
-`OPENSSL_cleanup()` from your application.
-
Secure Memory
-------------