Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

global unified freelist #1

Open
methane opened this issue Feb 13, 2017 · 0 comments
Open

global unified freelist #1

methane opened this issue Feb 13, 2017 · 0 comments

Comments

@methane
Copy link
Owner

methane commented Feb 13, 2017

No description provided.

methane pushed a commit that referenced this issue Feb 15, 2017
@Mariatta
Support "bpo-" in Misc/NEWS (#1) (#43)
af456b2 
Change the url to 3.5

(cherry picked from commit 79ab8be)

Contributed by Brett Cannon
methane pushed a commit that referenced this issue Feb 15, 2017
@Mariatta
[backport to 2.7] Change documentation's Show Source link to GitHub (…
52b8c55 
…#44)

* Support "bpo-" in Misc/NEWS (#1)
Change the url to 2.7

(cherry picked from commit 79ab8be)

* pyspecific.py: remove space after` bpo-`
@rurban rurban mentioned this issue Dec 1, 2016
Open
methane pushed a commit that referenced this issue Sep 4, 2017
@pylessard @tiran
bpo-30987 - Support for ISO-TP protocol in SocketCAN (python#2956)
a30f6d4 
* Added support for CAN_ISOTP protocol

* Added unit tests for CAN ISOTP

* Updated documentation for ISO-TP protocol

* Removed trailing whitespace in documentation

* Added blurb NEWS.d file

* updated Misc/ACKS

* Fixed broken unit test that was using isotp const outside of skippable section

* Removed dependecy over third party project

* Added implementation for getsockname + unit tests

* Missing newline at end of ACKS file

* Accidentally inserted a type in ACKS file

* Followed tiran changes review #1 recommendations

* Added spaces after comma
methane pushed a commit that referenced this issue Jun 15, 2020
@tiran
bpo-40955: Fix memory leak in subprocess module (pythonGH-20825)
0d3350d 
```
Direct leak of 8 byte(s) in 1 object(s) allocated from:
    #0 0x7f008bf19667 in __interceptor_malloc (/lib64/libasan.so.6+0xb0667)
    #1 0x7f007a0bee4a in subprocess_fork_exec /home/heimes/dev/python/cpython/Modules/_posixsubprocess.c:774
    #2 0xe0305b in cfunction_call Objects/methodobject.c:546
```

Signed-off-by: Christian Heimes <[email protected]>
methane pushed a commit that referenced this issue Jun 17, 2020
@miss-islington @tiran
bpo-40955: Fix memory leak in subprocess module (pythonGH-20825)
ee3f7fe 
```
Direct leak of 8 byte(s) in 1 object(s) allocated from:
    GH-0 0x7f008bf19667 in __interceptor_malloc (/lib64/libasan.so.6+0xb0667)
    GH-1 0x7f007a0bee4a in subprocess_fork_exec /home/heimes/dev/python/cpython/Modules/_posixsubprocess.c:774
    GH-2 0xe0305b in cfunction_call Objects/methodobject.c:546
```

Signed-off-by: Christian Heimes <[email protected]>
(cherry picked from commit 0d3350d)

Co-authored-by: Christian Heimes <[email protected]>
methane pushed a commit that referenced this issue Jan 29, 2021
@ssbr
bpo-40791: Make compare_digest more constant-time. (pythonGH-20444)
3172936 
* bpo-40791: Make compare_digest more constant-time.

The existing volatile `left`/`right` pointers guarantee that the reads will all occur, but does not guarantee that they will be _used_. So a compiler can still short-circuit the loop, saving e.g. the overhead of doing the xors and especially the overhead of the data dependency between `result` and the reads. That would change performance depending on where the first unequal byte occurs. This change removes that optimization.

(This is change #1 from https://bugs.python.org/issue40791 .)
methane pushed a commit that referenced this issue Feb 21, 2021
@miss-islington @ssbr
bpo-40791: Make compare_digest more constant-time. (pythonGH-20444)
c1bbca5 
* bpo-40791: Make compare_digest more constant-time.

The existing volatile `left`/`right` pointers guarantee that the reads will all occur, but does not guarantee that they will be _used_. So a compiler can still short-circuit the loop, saving e.g. the overhead of doing the xors and especially the overhead of the data dependency between `result` and the reads. That would change performance depending on where the first unequal byte occurs. This change removes that optimization.

(This is change GH-1 from https://bugs.python.org/issue40791 .)
(cherry picked from commit 3172936)

Co-authored-by: Devin Jeanpierre <[email protected]>
methane pushed a commit that referenced this issue Feb 21, 2021
@miss-islington @ssbr
bpo-40791: Make compare_digest more constant-time. (pythonGH-20444)
97136d7 
* bpo-40791: Make compare_digest more constant-time.

The existing volatile `left`/`right` pointers guarantee that the reads will all occur, but does not guarantee that they will be _used_. So a compiler can still short-circuit the loop, saving e.g. the overhead of doing the xors and especially the overhead of the data dependency between `result` and the reads. That would change performance depending on where the first unequal byte occurs. This change removes that optimization.

(This is change GH-1 from https://bugs.python.org/issue40791 .)
(cherry picked from commit 3172936)

Co-authored-by: Devin Jeanpierre <[email protected]>
methane pushed a commit that referenced this issue Feb 6, 2022
@vstinner
bpo-46600: Fix test_gdb.test_pycfunction() for clang -Og (pythonGH-31058
bebaa95 
)

Fix test_gdb.test_pycfunction() for Python built with clang -Og.
Tolerate inlined functions in the gdb traceback.

When _testcapimodule.c is built by clang -Og, _null_to_none() is
inlined in meth_varargs() and so gdb returns _null_to_none() as
the frame #1. If it's not inlined, meth_varargs() is the frame #1.
methane pushed a commit that referenced this issue Apr 19, 2022
@gpshead
pythongh-89455: Fix an uninitialized bool in exception print context. (…
861974b 
…python#91466)

Fix an uninitialized bool in exception print context.
    
`struct exception_print_context.need_close` was uninitialized.
    
Found by oss-fuzz in a test case running under the undefined behavior sanitizer.
    
https://oss-fuzz.com/testcase-detail/6217746058182656
    
```
Python/pythonrun.c:1241:28: runtime error: load of value 253, which is not a valid value for type 'bool'
    #0 0xbf2203 in print_chained cpython3/Python/pythonrun.c:1241:28
    #1 0xbea4bb in print_exception_cause_and_context cpython3/Python/pythonrun.c:1320:19
    #2 0xbea4bb in print_exception_recursive cpython3/Python/pythonrun.c:1470:13
    #3 0xbe9e39 in _PyErr_Display cpython3/Python/pythonrun.c:1517:9
```
    
Pretty obvious what the ommission was upon code inspection.
methane pushed a commit that referenced this issue Dec 8, 2023
@vstinner
Revert "pythongh-46376: Return existing pointer when possible in ctyp…
5a79d2a 
…es (#1… (python#108688)

This reverts commit 08447b5.

Revert also _ctypes.c changes of the PyDict_ContainsString() change,
commit 6726626.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@methane