llvm-project/clang/test/Sema/missing-dllimport.c

// RUN: %clang_cc1 -triple i686-pc-win32 -fms-extensions -verify %s

// Do not report that 'foo()' is redeclared without dllimport attribute.
// specified.

// expected-no-diagnostics
__declspec(dllimport) int __cdecl foo(void);
inline int __cdecl foo() { return 0; }
__declspec is not a core Clang language extension. Instead, require -fms-extensions or -fborland to enable the language extension. Note: __declspec is also temporarily enabled when compiling for a CUDA target because there are implementation details relying on __declspec(property) support currently. When those details change, __declspec should be disabled for CUDA targets. llvm-svn: 238238 2015-05-26 19:44:52 +00:00			`// RUN: %clang_cc1 -triple i686-pc-win32 -fms-extensions -verify %s`
Don't warn about functions redeclared without the dllimport attribute when -fms-extensions is enabled. Fixes <rdar://problem/7669559>. llvm-svn: 96721 2010-02-21 05:12:53 +00:00
An inline function redeclaration does not drop the dllimport attribute llvm-svn: 209449 2014-05-22 15:46:15 +00:00			`// Do not report that 'foo()' is redeclared without dllimport attribute.`
[clang] Remove rdar links; NFC We have a new policy in place making links to private resources something we try to avoid in source and test files. Normally, we'd organically switch to the new policy rather than make a sweeping change across a project. However, Clang is in a somewhat special circumstance currently: recently, I've had several new contributors run into rdar links around test code which their patch was changing the behavior of. This turns out to be a surprisingly bad experience, especially for newer folks, for a handful of reasons: not understanding what the link is and feeling intimidated by it, wondering whether their changes are actually breaking something important to a downstream in some way, having to hunt down strangers not involved with the patch to impose on them for help, accidental pressure from asking for potentially private IP to be made public, etc. Because folks run into these links entirely by chance (through fixing bugs or working on new features), there's not really a set of problematic links to focus on -- all of the links have basically the same potential for causing these problems. As a result, this is an omnibus patch to remove all such links. This was not a mechanical change; it was done by manually searching for rdar, radar, radr, and other variants to find all the various problematic links. From there, I tried to retain or reword the surrounding comments so that we would lose as little context as possible. However, because most links were just a plain link with no supporting context, the majority of the changes are simple removals. Differential Review: https://reviews.llvm.org/D158071 2023-08-28 12:13:42 -04:00			`// specified.`
Don't warn about functions redeclared without the dllimport attribute when -fms-extensions is enabled. Fixes <rdar://problem/7669559>. llvm-svn: 96721 2010-02-21 05:12:53 +00:00
An inline function redeclaration does not drop the dllimport attribute llvm-svn: 209449 2014-05-22 15:46:15 +00:00			`// expected-no-diagnostics`
Don't warn about functions redeclared without the dllimport attribute when -fms-extensions is enabled. Fixes <rdar://problem/7669559>. llvm-svn: 96721 2010-02-21 05:12:53 +00:00			`__declspec(dllimport) int __cdecl foo(void);`
			`inline int __cdecl foo() { return 0; }`