| // RUN: %clang_cc1 -emit-llvm-only -triple x86_64-linux-gnu -verify %s |
| // RUN: %clang_cc1 -emit-llvm-only -triple x86_64-apple-macosx -verify %s |
| // RUN: %clang_cc1 -emit-llvm-only -triple arm64-apple-macosx -verify %s |
| // RUN: not %clang_cc1 -triple x86_64-linux -emit-llvm-only -fdiagnostics-parseable-fixits %s 2>&1 | FileCheck %s |
| // RUN: not %clang_cc1 -triple x86_64-apple-macosx -emit-llvm-only -fdiagnostics-parseable-fixits %s 2>&1 | FileCheck %s |
| // RUN: not %clang_cc1 -triple arm64-apple-macosx -emit-llvm-only -fdiagnostics-parseable-fixits %s 2>&1 | FileCheck %s |
| |
| extern "C" { |
| __attribute__((used)) static void *resolve_foo() { return 0; } |
| namespace NS { |
| __attribute__((used)) static void *resolve_foo() { return 0; } |
| } // namespace NS |
| |
| // FIXME: This diagnostic is pretty confusing, the issue is that the existence |
| // of the two functions suppresses the 'alias' creation, and thus the ifunc |
| // resolution via the alias as well. In the future we should probably find |
| // some way to improve this diagnostic (likely by diagnosing when we decide |
| // this case suppresses alias creation). |
| __attribute__((ifunc("resolve_foo"))) void foo(); // expected-error{{ifunc must point to a defined function}} |
| // expected-note@-1 {{must refer to its mangled name}} |
| // expected-note@-2 {{function by that name is mangled as}} |
| // expected-note@-3 {{function by that name is mangled as}} |
| // CHECK: fix-it:"{{.*}}":{[[@LINE-4]]:16-[[@LINE-4]]:36}:"ifunc(\"_ZL11resolve_foov\")" |
| // CHECK: fix-it:"{{.*}}":{[[@LINE-5]]:16-[[@LINE-5]]:36}:"ifunc(\"_ZN2NSL11resolve_fooEv\")" |
| } |
| |
