Skip to content

Conversation

@pcanal
Copy link
Member

@pcanal pcanal commented Apr 29, 2025

LockCompilationDuringUserCodeExecutionRAII: to be used right before compiling/executing user code
InterpreterAccessRAII: to be used during loookups

@github-actions
Copy link

github-actions bot commented Apr 29, 2025

Test Results

    19 files      19 suites   3d 13h 56m 10s ⏱️
 2 748 tests  2 747 ✅ 0 💤 1 ❌
50 773 runs  50 772 ✅ 0 💤 1 ❌

For more details on these failures, see this check.

Results for commit bb3ca02.

♻️ This comment has been updated with latest results.

@hahnjo hahnjo requested a review from vgvassilev May 2, 2025 06:40
@hahnjo
Copy link
Member

hahnjo commented May 2, 2025

I don't really understand the semantic distinction between the two types: both access the interpreter and need to lock during compilation.

@pcanal
Copy link
Member Author

pcanal commented May 2, 2025

The 'difference' is that the user-code related one is intended to be later temporarily suspended (via EnterUserCodeRAII) during the actual user code execution while the new usages are meant to be use in places where there is no user code being called and thus the lock will actually be held continuously by the thread until it is released by the RAII.

Copy link
Member

@hahnjo hahnjo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

LockCompilationDuringUserCodeExecutionRAII: to be used right before compiling/executing user code
InterpreterAccessRAII: to be used during loookups
@pcanal pcanal force-pushed the master-cling-lock branch from 0aef56d to bb3ca02 Compare May 19, 2025 16:52
@dpiparo dpiparo merged commit 9dd3b80 into root-project:master May 21, 2025
21 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants