66f4a1399d
When implementing thread_local as a keyword in C23, we accidentally started using C++11 thread_local semantics when using that keyword instead of using C11 _Thread_local semantics. This oversight is fixed by pretending the user wrote _Thread_local instead. This doesn't have the best behavior in terms of diagnostics, but it does correct the semantic behavior. Fixes https://github.com/llvm/llvm-project/issues/70068 Fixes https://github.com/llvm/llvm-project/issues/69167
28 lines
1001 B
C
28 lines
1001 B
C
// RUN: %clang_cc1 -triple i686-pc-linux-gnu -std=c23 -emit-llvm -o - %s | FileCheck %s
|
|
|
|
// Ensure that thread_local and _Thread_local emit the same codegen. See
|
|
// https://github.com/llvm/llvm-project/issues/70068 for details.
|
|
|
|
void func(void) {
|
|
static thread_local int i = 12;
|
|
static _Thread_local int j = 13;
|
|
|
|
extern thread_local int k;
|
|
extern thread_local int l;
|
|
|
|
(void)k;
|
|
(void)l;
|
|
}
|
|
|
|
// CHECK: @func.i = internal thread_local global i32 12, align 4
|
|
// CHECK-NEXT: @func.j = internal thread_local global i32 13, align 4
|
|
// CHECK-NEXT: @k = external thread_local global i32, align 4
|
|
// CHECK-NEXT: @l = external thread_local global i32, align 4
|
|
|
|
// CHECK: define dso_local void @func()
|
|
// CHECK-NEXT: entry:
|
|
// CHECK-NEXT: %[[K:.+]] = call align 4 ptr @llvm.threadlocal.address.p0(ptr align 4 @k)
|
|
// CHECK-NEXT: load i32, ptr %[[K]], align 4
|
|
// CHECK-NEXT: %[[L:.+]] = call align 4 ptr @llvm.threadlocal.address.p0(ptr align 4 @l)
|
|
// CHECK-NEXT: load i32, ptr %[[L]], align 4
|