llvm-project/clang/test/CodeGenCXX/2009-08-11-VectorRetTy.cpp

// RUN: %clang_cc1 %s -emit-llvm -o /dev/null
typedef void (*Func) ();
typedef long long m64 __attribute__((__vector_size__(8), __may_alias__));
static inline m64 __attribute__((__always_inline__, __nodebug__)) _mm_set1_pi16() { return {}; }
template <class MM>
static void Bork() {
  const m64 mmx_0x00ff = _mm_set1_pi16();
}
struct A {};
Func arr[] = {
  Bork<A>
};
Migrate 2009-08-11-VectorRetTy.cpp from llvm/test/FrontendC++. llvm-svn: 138095 2011-08-19 21:50:59 +00:00			`// RUN: %clang_cc1 %s -emit-llvm -o /dev/null`
			`typedef void (*Func) ();`
			`typedef long long m64 __attribute__((__vector_size__(8), __may_alias__));`
[Clang] [NFC] Fix unintended `-Wreturn-type` warnings everywhere in the test suite (#123464) In preparation of making `-Wreturn-type` default to an error (as there is virtually no situation where you’d want to fall off the end of a function that is supposed to return a value), this patch fixes tests that have relied on this being only a warning, of which there seem to be 3 kinds: 1. Tests which for no apparent reason have a function that triggers the warning. I suspect that a lot of these were on accident (or from before the warning was introduced), since a lot of people will open issues w/ their problematic code in the `main` function (which is the one case where you don’t need to return from a non-void function, after all...), which someone will then copy, possibly into a namespace, possibly renaming it, the end result of that being that you end up w/ something that definitely is not `main` anymore, but which still is declared as returning `int`, and which still has no return statement (another reason why I think this might apply to a lot of these is because usually the actual return type of such problematic functions is quite literally `int`). A lot of these are really old tests that don’t use `-verify`, which is why no-one noticed or had to care about the extra warning that was already being emitted by them until now. 2. Tests which test either `-Wreturn-type`, `[[noreturn]]`, or what codegen and sanitisers do whenever you do fall off the end of a function. 3. Tests where I struggle to figure out what is even being tested (usually because they’re Objective-C tests, and I don’t know Objective-C), whether falling off the end of a function matters in the first place, and tests where actually spelling out an expression to return would be rather cumbersome (e.g. matrix types currently don’t support list initialisation, so I can’t write e.g. `return {}`). For tests that fall into categories 2 and 3, I just added `-Wno-error=return-type` to the `RUN` lines and called it a day. This was especially necessary for the former since `-Wreturn-type` is an analysis-based warning, meaning that it is currently impossible to test for more than one occurrence of it in the same compilation if it defaults to an error since the analysis pass is skipped for subsequent functions as soon as an error is emitted. I’ve also added `-Werror=return-type` to a few tests that I had already updated as this patch was previously already making the warning an error by default, but we’ve decided to split that into two patches instead. 2025-01-18 19:16:33 +01:00			`static inline m64 __attribute__((__always_inline__, __nodebug__)) _mm_set1_pi16() { return {}; }`
Migrate 2009-08-11-VectorRetTy.cpp from llvm/test/FrontendC++. llvm-svn: 138095 2011-08-19 21:50:59 +00:00			`template <class MM>`
			`static void Bork() {`
			`const m64 mmx_0x00ff = _mm_set1_pi16();`
			`}`
			`struct A {};`
			`Func arr[] = {`
			`Bork<A>`
			`};`