[Bug 250322] lang/python3{6,7,8,9}: Backport close_range patches

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250322

            Bug ID: 250322
           Summary: lang/python3{6,7,8,9}: Backport close_range patches
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: kevans at freebsd.org

Created attachment 218721
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=218721&action=edit
svn(1) diff against the ports tree

Worked out over BPO-40422 and BPO-40423, this is the culmination of months of
work to coordinate with Linux and get close_range(2) added to FreeBSD, then the
usage accepted into CPython. It has landed for Python 3.10 and here I've
backported it locally to all the supported Python 3 versions we have.

Note that this does include and supercede our previous closefrom(2) patches.
There was a lot of intersection between the work done, so this patch against
the ports tree does remove those patches from each of the ports in favor of
this patch. All the patches involved have been accepted and merged upstream.

This patch will bring a performance boost in some more situations on 12.2 and
13.0, as close_range exists there.

There is one additional patch sitting in an upstream PR that shuffles the
_Py_closerange implementation into a different file -- this is not important
for the backport, and the absence of that patch here will not realistically
cause any issues.

Q/A:
 * portlint (pre-existing issues)
 * testport (11.4/amd64, 12.1/i386, -CURRENT/amd64) (note that only
-CURRENT/amd64 currently has close_range, the other two did not)

-- 
You are receiving this mail because:
You are the assignee for the bug.