[all-commits] [llvm/llvm-project] 71d105: [CaptureTracking][NFC] Clarify usage expectations ...
Camsyn via All-commits
all-commits at lists.llvm.org
Mon Apr 14 09:06:55 PDT 2025
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 71d10590dbc041139644f00144513c7f487a94ba
https://github.com/llvm/llvm-project/commit/71d10590dbc041139644f00144513c7f487a94ba
Author: Camsyn <camsyn at foxmail.com>
Date: 2025-04-14 (Mon, 14 Apr 2025)
Changed paths:
M llvm/include/llvm/Analysis/CaptureTracking.h
Log Message:
-----------
[CaptureTracking][NFC] Clarify usage expectations in PointerMayBeCaptured comments (#132744)
Fixes issue #132739.
CaptureAnalysis only considers captures through the def-use chain of the
provided pointer, explicitly excluding captures of underlying values or
implicit captures like those involving external globals.
The previous comment for `PointerMayBeCaptured` did not clearly state
this limitation, leading to its incorrect usage in files such as
ThreadSanitizer.cpp and SanitizerMetadata.cpp.
This PR addresses this by refining the comments for the relevant APIs
within `PointerMayBeCaptured` to explicitly document this behavior.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list