> -----Original Message----- > From: Szabolcs Nagy via Phabricator [mailto:revi...@reviews.llvm.org] > Sent: Thursday, January 11, 2018 6:13 AM > To: Blower, Melanie <melanie.blo...@intel.com>; Keane, Erich > <erich.ke...@intel.com>; sca...@apple.com; roger.ferreriba...@arm.com; > sjoerd.mei...@arm.com; jle...@google.com; > hubert.reinterpretc...@gmail.com > Cc: szabolcs.n...@arm.com; james.greenha...@arm.com; > eli.fried...@gmail.com; efrie...@codeaurora.org; rich...@metafoo.co.uk; > cfe-commits@lists.llvm.org; mlek...@skidmore.edu; jkor...@apple.com; > shen...@google.com; t...@google.com > Subject: [PATCH] D40673: Add _Float128 as alias to __float128 to enable > compilations on Fedora27/glibc2-26 > > nsz added a comment. > > if clang wants to provide _Float128 then the f128 constant suffix (specified > by > TS18661-3) and __builtin_inff128, __builtin_nanf128, __builtin_nansf128, > __builtin_huge_valf128 (gcc builtins required by math.h) need to be supported > too. [Blower, Melanie] You are right, there are f128 builtins missing and also we need the f128 literal suffix. There may be other builtins missing as well. Some of glibc sources refer to __FLT_EVAL_METHOD_TS_18661_3__ does clang support that? > > as this patch is committed clang is broken (cannot use glibc headers) on any > target where long double is quad precision (aarch64, mips64, s390, sparc64, > riscv64) even if glibc fixes the >=gcc-7 check to something that works for > clang: > either the _Float128 typedef conflicts with the definition by clang or the > suffixes/builtins are missing. > > > Repository: > rC Clang > > https://reviews.llvm.org/D40673 > >
_______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
