Fix build of test port program
Use +clint0 in compiler's test suites
Check for more return mismatches

All expressions but calls and primops are now checked for return mismatches.
Handle return mismatches for calls and primops

Only exit BIFs and the match_fail primop are allowed to run where more than one
value is expected.
Remove obsolete comment in core_lint
Fix error printouts to not crash
Merge branch 'lars/orber/dual_ipv6_and_ipv4' into maint-17

* lars/orber/dual_ipv6_and_ipv4:
  [orber] Fix bug in testcase
  [orber] Fix malformed macros
  [orber] Add test suite for ORB with dual ipv4/ipv6 configuration
  [orber] Update documentation and fix testcase for IPv4/IPv6
  [orber] Update testcases and fixed some minor faults
  [orber] Remove unused file corba_request.erl
  [orber] Remove a define of ORBVSN when compiling orbers erlang modules
  [orber] Add possibilty to configure orber to run in both IPv4 and IPv6
Merge branch 'raimo/snmp/ipv4+ipv6/OTP-12020' into maint-17

* refs/heads/fetch-and-merge.maint-17-opu/FETCH_HEAD/54676: (46 commits)
  Fix error printouts to not crash
  Improve ct_snmp test cases
  Fix misspelled community in manager
  Rearrange test suite group structure
  Fix testcase for really dual ip
  Adjust test cases for daily builds
  Fix call to non-existent function
  Fix test manager in agent tests for IPv6
  Call new Net-SNMP test suite from top suite
  Improve external snmp commands args
  Test inform to dual transports
  Write list of trap targets
  Improve dual stack test suite
  Use {ipv6_v6only, true}
  Remove commented out code
  Add dual_ip tests in snmp_to_snmpnet_SUITE
  Silence logging from agent net_if at shutdown
  Rewrite agent for IPv4 + IPv6
  snmp: Add inform test
  snmp: Add new test suite
  ...
Update release notes
Updated OTP version
Fix emigrate bug in erts_port_task_schedule()

While current run-queue lock is unlocked in the call to
erts_check_emigration_need() from erts_port_task_schedule() the
port can be migrated to another run-queue by another thread.
The code in erts_port_task_schedule() needs to check if this
has occurred when returning from erts_check_emigration_need(), and
if so respect the migration decision. When this was not done,
the thread calling erts_port_task_schedule() held the wrong
run-queue lock which caused invalid updates of the port task queue.

This bug was automatically fixed by the rewrites in the branch
rickard/r16b/port-optimizations-fixes/OTP-10336 (commit
56cef897ca3ad2377e34a6ea5800a54a28cbeb6e) introduced in erts-5.10
and do not effect erts versions after that.
correction of huge status bar

following the last evolution - use wxStatusBar:new(Frame) then wxFrame:setStatusBar(Frame, StatusBar), the status bar use the full space available in frame.
move the creation of the status bar after the creation of the notebook and the mainsizer.

it is ok on windows 7 64bits, no other test done so far.
Merge branch 'lukas/erts/malloc_failure_errors/OTP-12085' into maint

* lukas/erts/malloc_failure_errors/OTP-12085:
  erts: Print error reason when malloc fails
Merge branch 'maint'

* maint:
  erts: Print error reason when malloc fails
ssl: Correct handling of certificate_types in Certificate Requests

FROM TLS 1.2 RFC:
   The interaction of the certificate_types and
   supported_signature_algorithms fields is somewhat complicated.
   certificate_types has been present in TLS since SSLv3, but was
   somewhat underspecified.  Much of its functionality is superseded by
   supported_signature_algorithms.  The following rules apply:

   -  Any certificates provided by the client MUST be signed using a
      hash/signature algorithm pair found in
      supported_signature_algorithms.

   -  The end-entity certificate provided by the client MUST contain a
      key that is compatible with certificate_types.  If the key is a
      signature key, it MUST be usable with some hash/signature
      algorithm pair in supported_signature_algorithms.

   -  For historical reasons, the names of some client certificate types
      include the algorithm used to sign the certificate.  For example,
      in earlier versions of TLS, rsa_fixed_dh meant a certificate
      signed with RSA and containing a static DH key.  In TLS 1.2, this
      functionality has been obsoleted by the
      supported_signature_algorithms, and the certificate type no longer
      restricts the algorithm used to sign the certificate.  For
      example, if the server sends dss_fixed_dh certificate type and
      {{sha1, dsa}, {sha1, rsa}} signature types, the client MAY reply
      with a certificate containing a static DH key, signed with RSA-
      SHA1.
public_key: Correct ASN-1 spec
public_key: Correct ASN1-type EcpkParameters in PEM handling
Merge branch 'maint-17' into maint
Merge branch 'maint'

Conflicts:
	OTP_VERSION
Merge branch 'tuncer/sanitizers' into maint

OTP-12081

* tuncer/sanitizers:
  Implement --enable-sanitizers[=sanitizers]