llvm-project/clang/test/CodeGen/mips64-f128-literal.c

// RUN: %clang -target mips64el-unknown-linux -O3 -S -mabi=n64 -o - -emit-llvm %s | FileCheck %s

typedef long double LD;

// CHECK: ret fp128

LD foo0() {
  return 2.625L;
}
The clang driver has a fairly fancy support for executing gcc instead of clang itself. This dates back to clang's early days and while it looks like some of it is still used (for kext for example), other parts are probably dead. Remove the -ccc-clang-archs option and associated code. I don't think there is any remaining setup where clang doesn't support an architecture but it can expect an working gcc cross compiler to be available. A nice side effect is that tests no longer need to differentiate architectures that are included in production builds of clang and those that are not. llvm-svn: 165545 2012-10-10 04:46:28 +08:00			`// RUN: %clang -target mips64el-unknown-linux -O3 -S -mabi=n64 -o - -emit-llvm %s \| FileCheck %s`
Add field IsIEEE in FloatingLiteral to distinguish between different 128-bit floating point formats. llvm-svn: 147887 2012-01-11 06:40:09 +08:00
			`typedef long double LD;`

			`// CHECK: ret fp128`

			`LD foo0() {`
			`return 2.625L;`
			`}`