Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2020-02-19T21:37:59+00:00 2020-02-19T21:37:59+00:00 Richard Smith richard@metafoo.co.uk 2020-02-19T00:13:23+00:00 urn:sha1:5175565cf154aede57354336102a7f6e15a16a20 user interface and documentation, and update __cplusplus for C++20. WG21 considers the C++20 standard to be finished (even though it still has some more steps to pass through in the ISO process). The old flag names are accepted for compatibility, as usual, and we still have lots of references to C++2a in comments and identifiers; those can be cleaned up separately. (cherry picked from commit 24ad121582454e625bdad125c90d9ac0dae948c8) 2020-01-24T01:03:16+00:00 Saar Raz saar@raz.email 2020-01-24T00:59:14+00:00 urn:sha1:901a7890c0e65060511c43d55fc347a1a5cb54ff Concepts will be available with Clang 10 - update cxx_status.html to reflect the papers that have been implemented. (cherry picked from commit f394d22fa82df03eaf72bf1876e2d63bbe6cd00f) 2020-01-10T02:24:06+00:00 Richard Smith richard@metafoo.co.uk 2020-01-09T23:31:56+00:00 urn:sha1:f041e9ad706aee7987c5299427c33424fcabbd0d The language wording change forgot to update overload resolution to rank implicit conversion sequences based on qualification conversions in reference bindings. The anticipated resolution for that oversight is implemented here -- we order candidates based on qualification conversion, not only on top-level cv-qualifiers, including ranking reference bindings against non-reference bindings if they differ in non-top-level qualification conversions. For OpenCL/C++, this allows reference binding between pointers with differing (nested) address spaces. This makes the behavior of reference binding consistent with that of implicit pointer conversions, as is the purpose of this change, but that pre-existing behavior for pointer conversions is itself probably not correct. In any case, it's now consistently the same behavior and implemented in only one place. This reinstates commit de21704ba96fa80d3e9402f12c6505917a3885f4, reverted in commit d8018233d1ea4234de68d5b4593abd773db79484, with workarounds for some overload resolution ordering problems introduced by CWG2352. 2020-01-03T19:13:40+00:00 Alexander Lanin alex@lanin.de 2020-01-03T19:13:40+00:00 urn:sha1:e5a56f2d50ce1939eba4fddbeb9c8e032db4fc95 The patch files section is redundant to https://llvm.org/docs/GettingStarted.html. There is nothing clang specific here. We are talking about a monorepo after all. While it may seem nice to have one single clang page which explains everything, it's not: It doesn't cover the topics in sufficient depth, it's redundant to other pages and it's hard to keep it up to date as we see with the svn instructions. 2019-12-27T20:27:20+00:00 David Blaikie dblaikie@gmail.com 2019-12-27T20:17:01+00:00 urn:sha1:d8018233d1ea4234de68d5b4593abd773db79484 This reverts commit de21704ba96fa80d3e9402f12c6505917a3885f4. Regressed/causes this to error due to ambiguity: void f(const int * const &); void f(int *); int main() { int * x; f(x); } (in case it's important - the original case where this turned up was a member function overload in a class template with, essentially: f(const T1&) f(T2*) (where T1 == X const *, T2 == X)) It's not super clear to me if this ^ is expected behavior, in which case I'm sorry about the revert & happy to look into ways to fix the original code. 2019-12-21T09:52:39+00:00 Sylvestre Ledru sledru@mozilla.com 2019-12-21T09:49:15+00:00 urn:sha1:7ece0ee3dd7cd717b4365c5c48710e5ba1f702bb 2019-12-21T09:52:30+00:00 Sylvestre Ledru sledru@mozilla.com 2019-12-21T09:48:16+00:00 urn:sha1:a0ce6155734eaaea315dc82579b230b172fb8ccc 2019-12-21T09:46:45+00:00 Sylvestre Ledru sledru@mozilla.com 2019-12-21T09:46:45+00:00 urn:sha1:384a287a999987ad0989624eb785293d38f9b710 2019-12-20T02:37:55+00:00 Richard Smith richard@metafoo.co.uk 2019-12-19T19:15:47+00:00 urn:sha1:de21704ba96fa80d3e9402f12c6505917a3885f4 The language wording change forgot to update overload resolution to rank implicit conversion sequences based on qualification conversions in reference bindings. The anticipated resolution for that oversight is implemented here -- we order candidates based on qualification conversion, not only on top-level cv-qualifiers. For OpenCL/C++, this allows reference binding between pointers with differing (nested) address spaces. This makes the behavior of reference binding consistent with that of implicit pointer conversions, as is the purpose of this change, but that pre-existing behavior for pointer conversions is itself probably not correct. In any case, it's now consistently the same behavior and implemented in only one place. 2019-12-19T22:54:29+00:00 Artem Dergachev artem.dergachev@gmail.com 2019-12-19T22:21:02+00:00 urn:sha1:b284005072122fe4af879725e3c8090009f89ca0 Method '-[NSCoder decodeValueOfObjCType:at:]' is not only deprecated but also a security hazard, hence a loud check. Differential Revision: https://reviews.llvm.org/D71728