dfa8732d05
For the AllocToken pass to accurately calculate token ID hints, we need to attach `!alloc_token` metadata for allocation calls. Unlike new expressions, untyped allocation calls (like `malloc`, `calloc`, `::operator new(..)`, `__builtin_operator_new`, etc.) have no syntactic type associated with them. For -fsanitize=alloc-token, type hints are sufficient, and we can attempt to infer the type based on common idioms. When encountering allocation calls (with `__attribute__((malloc))` or `__attribute__((alloc_size(..))`), attach `!alloc_token` by inferring the allocated type from (a) sizeof argument expressions such as `malloc(sizeof(MyType))`, and (b) casts such as `(MyType*)malloc(4096)`. Note that non-standard allocation functions with these attributes are not instrumented by default. Use `-fsanitize-alloc-token-extended` to instrument them as well. Link: https://discourse.llvm.org/t/rfc-a-framework-for-allocator-partitioning-hints/87434 --- This change is part of the following series: 1. https://github.com/llvm/llvm-project/pull/160131 2. https://github.com/llvm/llvm-project/pull/156838 3. https://github.com/llvm/llvm-project/pull/162098 4. https://github.com/llvm/llvm-project/pull/162099 5. https://github.com/llvm/llvm-project/pull/156839 6. https://github.com/llvm/llvm-project/pull/156840 7. https://github.com/llvm/llvm-project/pull/156841 8. https://github.com/llvm/llvm-project/pull/156842
35 lines
1.4 KiB
C
35 lines
1.4 KiB
C
// Test optimization pipelines do not interfere with AllocToken lowering, and we
|
|
// pass on function attributes correctly.
|
|
//
|
|
// RUN: %clang_cc1 -fsanitize=alloc-token -triple x86_64-linux-gnu -emit-llvm %s -o - | FileCheck %s
|
|
// RUN: %clang_cc1 -O1 -fsanitize=alloc-token -triple x86_64-linux-gnu -emit-llvm %s -o - | FileCheck %s
|
|
// RUN: %clang_cc1 -O2 -fsanitize=alloc-token -triple x86_64-linux-gnu -emit-llvm %s -o - | FileCheck %s
|
|
|
|
typedef __typeof(sizeof(int)) size_t;
|
|
|
|
void *malloc(size_t size);
|
|
|
|
// CHECK-LABEL: @test_malloc(
|
|
// CHECK: call{{.*}} ptr @__alloc_token_malloc(i64 noundef 4, i64 2689373973731826898){{.*}} !alloc_token [[META_INT:![0-9]+]]
|
|
void *test_malloc() {
|
|
return malloc(sizeof(int));
|
|
}
|
|
|
|
// CHECK-LABEL: @no_sanitize_malloc(
|
|
// CHECK: call{{.*}} ptr @malloc(i64 noundef 4)
|
|
void *no_sanitize_malloc(size_t size) __attribute__((no_sanitize("alloc-token"))) {
|
|
return malloc(sizeof(int));
|
|
}
|
|
|
|
// By default, we should not be touching malloc-attributed non-libcall
|
|
// functions: there might be an arbitrary number of these, and a compatible
|
|
// allocator will only implement standard allocation functions.
|
|
void *nonstandard_malloc(size_t size) __attribute__((malloc));
|
|
// CHECK-LABEL: @test_nonlibcall_malloc(
|
|
// CHECK: call{{.*}} ptr @nonstandard_malloc(i64 noundef 4){{.*}} !alloc_token [[META_INT]]
|
|
void *test_nonlibcall_malloc() {
|
|
return nonstandard_malloc(sizeof(int));
|
|
}
|
|
|
|
// CHECK: [[META_INT]] = !{!"int", i1 false}
|