[all-commits] [llvm/llvm-project] f06737: [Instrumentor] Introduce BasePointerIO to communic...
Johannes Doerfert via All-commits
all-commits at lists.llvm.org
Thu May 28 12:46:10 PDT 2026
Branch: refs/heads/users/jdoerfert/instrumentor_base_pointer
Home: https://github.com/llvm/llvm-project
Commit: f0673720f9623f057e2f7c20a1b93877127aa5ef
https://github.com/llvm/llvm-project/commit/f0673720f9623f057e2f7c20a1b93877127aa5ef
Author: Johannes Doerfert <jdoerfert.llvm at gmail.com>
Date: 2026-05-28 (Thu, 28 May 2026)
Changed paths:
M llvm/include/llvm/Transforms/IPO/Instrumentor.h
M llvm/lib/Transforms/IPO/Instrumentor.cpp
M llvm/test/Instrumentation/Instrumentor/alloca_and_function.ll
M llvm/test/Instrumentation/Instrumentor/default_config.json
M llvm/test/Instrumentation/Instrumentor/module_and_globals.ll
Log Message:
-----------
[Instrumentor] Introduce BasePointerIO to communicate base pointer information
Loads, stores, and later probably calls, can request a base pointer info
object from the user runtime. This object is queried right after the
base pointer of the operation is defined, and then passed to the
pre/post runtime calls of the loads and stores. This allows users to
inspect pointers early and once, but provide the analysis results to all
operations that might be executed in loops. A potential use case is to
lookup the size and start of the underlying object and then provide
those to the access runtime calls for in-bounds checking.
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