{"push_id":2989645534,"size":22,"distinct_size":22,"ref":"refs/heads/master","head":"dfa39ffd088e0a66bb88239556b029ebb8fc57fc","before":"6e5e0556a753b7ab4e4e59e0c48474b2c7e5b91e","commits":[{"sha":"33c2e18eaf5f30aacf9a9c7da8ca71781fdc4272","author":{"name":"Yuka Takahashi","email":"a303e2e6270912310689301f23a968169714facc@gmail.com"},"message":"[bash-autocompletion] Fix bug when a flag ends with '='\n\nThere was a bug that when a flag ends with '=' and no value was suggested,\nclang autocompletes the flag itself.\nFor example, in bash, it looked like this:\n```\n$ clang -fmodule-file=[tab]\n-> $clang -fmodule-file=-fmodule-file\n```\nThis is not what we expect. We expect a file autocompletion when no value\nwas found. With this patch, pressing tab suggests files in the current\ndirectory.\n\nReviewers: teemperor, ruiu\n\nSubscribers: cfe-commits\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345121 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/33c2e18eaf5f30aacf9a9c7da8ca71781fdc4272"},{"sha":"b06c0831376fdaa2ddce2110d57e7d5369db5bb8","author":{"name":"Ilya Biryukov","email":"eceaa92c40d19b4bf82eb67a163fa5c88b627d2b@google.com"},"message":"[Sema] Do not show unused parameter warnings when body is skipped\n\nSummary: Without the function body, we cannot determine is parameter was used.\n\nReviewers: ioeric, sammccall\n\nReviewed By: sammccall\n\nSubscribers: arphaman, cfe-commits\n\nDifferential Revision: https://reviews.llvm.org/D53456\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345122 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/b06c0831376fdaa2ddce2110d57e7d5369db5bb8"},{"sha":"589b42244bedcf5d2803feea65e02245fc1de341","author":{"name":"Aaron Ballman","email":"5a7a6a189b47cd31d24667a751e4003cd04eced5@aaronballman.com"},"message":"Support accepting __gnu__ as a scoped attribute namespace that aliases to gnu.\n\nThis is useful in libstdc++ to avoid clashes with identifiers in the user's namespace.\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345132 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/589b42244bedcf5d2803feea65e02245fc1de341"},{"sha":"31374564c244b20790a6597dada744a2b53eac72","author":{"name":"Yuka Takahashi","email":"a303e2e6270912310689301f23a968169714facc@gmail.com"},"message":"[autocompletion] Handle the space before pressing tab\n\nSummary:\nDistinguish \"--autocomplete=-someflag\" and \"--autocomplete=-someflag,\"\nbecause the latter indicates that the user put a space before pushing tab\nwhich should end up in a file completion.\n\nDifferential Revision: https://reviews.llvm.org/D53639\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345133 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/31374564c244b20790a6597dada744a2b53eac72"},{"sha":"abaf72c02d9ce6cc9d53b99fd0851ebe66cef129","author":{"name":"Eric Liu","email":"7f19b946fdf9b9340ac797a6f30cacd117523ba8@google.com"},"message":"[CodeComplete] Expose InBaseClass signal in code completion results.\n\nSummary:\nNo new tests as the existing tests for result priority should give us\ncoverage. Also as the new flag is trivial enough, I'm reluctant to plumb the\nflag to c-index-test output.\n\nReviewers: ilya-biryukov\n\nReviewed By: ilya-biryukov\n\nSubscribers: cfe-commits\n\nDifferential Revision: https://reviews.llvm.org/D53635\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345135 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/abaf72c02d9ce6cc9d53b99fd0851ebe66cef129"},{"sha":"212daa42ee33def6e7983401a6101553e24dc046","author":{"name":"Erich Keane","email":"ec9f61fe526c14bb62c55d7c978f025ee6b3583d@intel.com"},"message":"Remove a pair of unused dispatch multiversion declarations.\n\nThese declarations somehow survived a cleanup that combined them with the target\nmultiversioning functions.  This patch removes them as they are no\nlonger necessary or used.\n\nChange-Id: I318286401ace63bef1aa48018dabb25be0117ca0\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345145 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/212daa42ee33def6e7983401a6101553e24dc046"},{"sha":"7373e8384209e98c35fbba448d0c8538c488a363","author":{"name":"Kadir Cetinkaya","email":"f7d50215dcda8033719c767196a61e83068546ca@google.com"},"message":"[clang] Introduce new completion context types\n\nSummary: New name suggestions were being used in places where existing names should have been used, this patch tries to fix some of those situations.\n\nReviewers: sammccall\n\nReviewed By: sammccall\n\nSubscribers: arphaman, cfe-commits\n\nDifferential Revision: https://reviews.llvm.org/D53191\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345152 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/7373e8384209e98c35fbba448d0c8538c488a363"},{"sha":"09c4b455c82c3b8b949a19a7441335aa54f81cda","author":{"name":"Saleem Abdulrasool","email":"d3629432f14a71b62e796d32d075121c69cf67de@compnerd.org"},"message":"AST: unindent CFConstantStringDecl by inverting condition (NFC)\n\nUnindent the body of the function by inverting check at the top.  This is in\npreparation for supporting CFString's new ABI with swift.  NFC.\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345159 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/09c4b455c82c3b8b949a19a7441335aa54f81cda"},{"sha":"200207c0f1780bf30c7c532339507e501b8d595d","author":{"name":"Saleem Abdulrasool","email":"d3629432f14a71b62e796d32d075121c69cf67de@compnerd.org"},"message":"CodeGen: extract some local variables in CFConstantString creation (NFC)\n\nExtract the reference to the ASTContext and Triple and use them throughout the\nfunction.  This is simply a cosmetic cleanup while in the area.  NFC.\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345160 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/200207c0f1780bf30c7c532339507e501b8d595d"},{"sha":"c83cf570cd01a948fc0f209616379373f83043b9","author":{"name":"Craig Topper","email":"0c9ca018c303606191d06dd2c0bdf1206717c3f3@intel.com"},"message":"[CodeGen] Update min-legal-vector width based on function argument and return types\n\nThis is a continuation of my patches to inform the X86 backend about what the largest IR types are in the function so that we can restrict the backend type legalizer to prevent 512-bit vectors on SKX when -mprefer-vector-width=256 is specified if no explicit 512 bit vectors were specified by the user.\n\nThis patch updates the vector width based on the argument and return types of the current function and from the types of any functions it calls. This is intended to make sure the backend type legalizer doesn't disturb any types that are required for ABI.\n\nDifferential Revision: https://reviews.llvm.org/D52441\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345168 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/c83cf570cd01a948fc0f209616379373f83043b9"},{"sha":"dd2b9dd64f8c056547fe8a9448ca3d424767e106","author":{"name":"Krzysztof Parzyszek","email":"c75c6ffbe1757b9a0c4a980ebbd301c4f55ecd30@codeaurora.org"},"message":"[Hexagon] Flip hexagon-autohvx to be true by default\n\nThis will allow other generators of LLVM IR to use the auto-vectorizer\nwithout having to change that flag.\n\nNote: on its own, this patch will disable auto-vectorization on Hexagon\nin all cases, regardless of the -fvectorize flag. There is a companion\nLLVM patch that together with this one forms an NFC for clang users.\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345170 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/dd2b9dd64f8c056547fe8a9448ca3d424767e106"},{"sha":"f377c186fc4d7cd67698ab0c9e693bb195d3efe9","author":{"name":"Craig Topper","email":"0c9ca018c303606191d06dd2c0bdf1206717c3f3@intel.com"},"message":"[CodeGen] Update test checks missed in r345168.\n\nThese tests don't run unless the aarch64 target is registered and my testing had been on an x86 only build directory.\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345176 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/f377c186fc4d7cd67698ab0c9e693bb195d3efe9"},{"sha":"8d3394cba221c94f6732da891ac9a6e5f46b1a1b","author":{"name":"Alexey Bataev","email":"42c60520d22f29ab4fbd7ab379c1a50cda8b3dfa@hotmail.com"},"message":"[OPENMP]Fix PR39366: do not try to private field if it is not captured.\n\nThe compiler is crashing if we trying to post-capture the fields\nimplicitly captured inside of the task constructs. Seems, this kind of\nprocessing is not supported and such fields should not be\nfirstprivatized.\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345177 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/8d3394cba221c94f6732da891ac9a6e5f46b1a1b"},{"sha":"3f24b3520083253f098a52d181b9418d57a61816","author":{"name":"Alexey Bataev","email":"42c60520d22f29ab4fbd7ab379c1a50cda8b3dfa@hotmail.com"},"message":"Do not always request an implicit taskgroup region inside the kmpc_taskloop function\n\nSummary:\nFor the following code:\n```\n    int i;\n    #pragma omp taskloop\n    for (i = 0; i < 100; ++i)\n    {}\n\n    #pragma omp taskloop nogroup\n    for (i = 0; i < 100; ++i)\n    {}\n```\n\nClang emits the following LLVM IR:\n\n```\n ...\n  call void @__kmpc_taskgroup(%struct.ident_t* @0, i32 %0)\n  %2 = call i8* @__kmpc_omp_task_alloc(%struct.ident_t* @0, i32 %0, i32 1, i64 80, i64 8, i32 (i32, i8*)* bitcast (i32 (i32, %struct.kmp_task_t_with_privates*)* @.omp_task_entry. to i32 (i32, i8*)*))\n  ...\n  call void @__kmpc_taskloop(%struct.ident_t* @0, i32 %0, i8* %2, i32 1, i64* %8, i64* %9, i64 %13, i32 0, i32 0, i64 0, i8* null)\n  call void @__kmpc_end_taskgroup(%struct.ident_t* @0, i32 %0)\n\n  ...\n  %15 = call i8* @__kmpc_omp_task_alloc(%struct.ident_t* @0, i32 %0, i32 1, i64 80, i64 8, i32 (i32, i8*)* bitcast (i32 (i32, %struct.kmp_task_t_with_privates.1*)* @.omp_task_entry..2 to i32 (i32, i8*)*))\n  ...\n  call void @__kmpc_taskloop(%struct.ident_t* @0, i32 %0, i8* %15, i32 1, i64* %21, i64* %22, i64 %26, i32 0, i32 0, i64 0, i8* null)\n\n```\n\nThe first set of instructions corresponds to the first taskloop construct. It is important to note that the implicit taskgroup region associated with the taskloop construct has been materialized in our IR:  the `__kmpc_taskloop` occurs inside a taskgroup region. Note also that this taskgroup region does not exist in our second taskloop because we are using the `nogroup` clause.\n\nThe issue here is the 4th argument of the kmpc_taskloop call, starting from the end,  is always a zero. Checking the LLVM OpenMP RT implementation, we see that this argument corresponds to the nogroup parameter:\n\n```\nvoid __kmpc_taskloop(ident_t *loc, int gtid, kmp_task_t *task, int if_val,\n                     kmp_uint64 *lb, kmp_uint64 *ub, kmp_int64 st, int nogroup,\n                     int sched, kmp_uint64 grainsize, void *task_dup);\n```\n\nSo basically we always tell to the RT to do another taskgroup region. For the first taskloop, this means that we create two taskgroup regions. For the second example, it means that despite the fact we had a nogroup clause we are going to have a taskgroup region, so we unnecessary wait until all descendant tasks have been executed.\n\nReviewers: ABataev\n\nReviewed By: ABataev\n\nSubscribers: rogfer01, cfe-commits\n\nDifferential Revision: https://reviews.llvm.org/D53636\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345180 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/3f24b3520083253f098a52d181b9418d57a61816"},{"sha":"8572787b77cee3bfc13b67ea813eb6fb57192799","author":{"name":"Konstantin Zhuravlyov","email":"237b71dc3aa2b03e82075d578a7ddace3cbd7f67@outlook.com"},"message":"AMDGPU: Handle gfx909 in AMDGPUTargetInfo::initFeatureMap\n\n+ add required tests\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345181 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/8572787b77cee3bfc13b67ea813eb6fb57192799"},{"sha":"087ec178eee519a57d948e10e279c7e5af50f065","author":{"name":"Tim Renouf","email":"065b3514bf1e64691be1046036fd6fc442291c39@botech.co.uk"},"message":"Add gfx909 to GPU Arch\n\nSubscribers: jholewinski, cfe-commits\n\nDifferential Revision: https://reviews.llvm.org/D53558\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345198 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/087ec178eee519a57d948e10e279c7e5af50f065"},{"sha":"6f47cdd51341344c0e32630e19e72c94cd25f34e","author":{"name":"Eric Fiselier","email":"96f164ad4d9b2b0dacf8ebee2bb1eeb3aa69adf1@efcs.ca"},"message":"[SemaCXX] Unconfuse Clang when std::align_val_t is unscoped in C++03\n\nSummary:\nWhen -faligned-allocation is specified in C++03 libc++ defines std::align_val_t as an unscoped enumeration type (because Clang didn't provide scoped enumerations as an extension until 8.0).\nUnfortunately Clang confuses the `align_val_t` overloads of delete with the sized deallocation overloads which aren't enabled. This caused Clang to call the aligned deallocation function as if it were the sized deallocation overload.\n\nFor example: https://godbolt.org/z/xXJELh\n\nThis patch fixes the confusion.\n\nReviewers: rsmith, EricWF\n\nReviewed By: EricWF\n\nSubscribers: cfe-commits\n\nDifferential Revision: https://reviews.llvm.org/D53508\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345211 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/6f47cdd51341344c0e32630e19e72c94cd25f34e"},{"sha":"22fe7cf15e0aafad091c7bbc1cdcf3dc5fb3a1ea","author":{"name":"Volodymyr Sapsai","email":"96bd0c2df6a109067a023203e45b9542ed83f609@apple.com"},"message":"[VFS] Remove 'ignore-non-existent-contents' attribute for YAML-based VFS.\n\n'ignore-non-existent-contents' stopped working after r342232 in a way\nthat the actual attribute value isn't used and it works as if it is\nalways `true`.\n\nCommon use case for VFS iteration is iterating through files in umbrella\ndirectories for modules. Ability to detect if some VFS entries point to\nnon-existing files is nice but non-critical. Instead of adding back\nsupport for `'ignore-non-existent-contents': false` I am removing the\nattribute, because such scenario isn't used widely enough and stricter\nchecks don't provide enough value to justify the maintenance.\n\nrdar://problem/45176119\n\nReviewers: bruno\n\nReviewed By: bruno\n\nSubscribers: hiraditya, dexonsmith, sammccall, cfe-commits\n\nDifferential Revision: https://reviews.llvm.org/D53228\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345212 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/22fe7cf15e0aafad091c7bbc1cdcf3dc5fb3a1ea"},{"sha":"925e04d232a6c9abaa949f19689b9b443e6beeba","author":{"name":"Saleem Abdulrasool","email":"d3629432f14a71b62e796d32d075121c69cf67de@compnerd.org"},"message":"Driver,CodeGen: introduce support for Swift CFString layout\n\nAdd a new driver level flag `-fcf-runtime-abi=` that allows one to specify the\nruntime ABI for CoreFoundation.  This controls the language interoperability.\nIn particular, this is relevant for generating the CFConstantString classes\n(primarily through the `__builtin___CFStringMakeConstantString` builtin) which\nconstruct a reference to the \"CFObject\"'s `isa` field.  This type differs\nbetween swift 4.1 and 4.2+.\n\nValid values for the new option include:\n  - objc [default behaviour] - enable ObjectiveC interoperability\n  - swift-4.1 - enable interoperability with swift 4.1\n  - swift-4.2 - enable interoperability with swift 4.2\n  - swift-5.0 - enable interoperability with swift 5.0\n  - swift [alias] - target the latest swift ABI\n\nFurthermore, swift 4.2+ changed the layout for the CFString when building\nCoreFoundation *without* ObjectiveC interoperability.  In such a case, a field\nwas added to the CFObject base type changing it from: <{ const int*, int }> to\n<{ uintptr_t, uintptr_t, uint64_t }>.\n\nIn swift 5.0, the CFString type will be further adjusted to change the length\nfrom a uint32_t on everything but BE LP64 targets to uint64_t.\n\nNote that the default behaviour for clang remains unchanged and the new layout\nmust be explicitly opted into via `-fcf-runtime-abi=swift*`.\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345222 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/925e04d232a6c9abaa949f19689b9b443e6beeba"},{"sha":"3896e0bc2d0225106d57e9c70095cc27c9f86df1","author":{"name":"Eric Fiselier","email":"96f164ad4d9b2b0dacf8ebee2bb1eeb3aa69adf1@efcs.ca"},"message":"Revert \"[SemaCXX] Unconfuse Clang when std::align_val_t is unscoped in C++03\"\n\nThis reverts commit 6f47cdd51341344c0e32630e19e72c94cd25f34e.\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@345225 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/UofT-EcoSystem/clang/commits/3896e0bc2d0225106d57e9c70095cc27c9f86df1"}]}
{"actor":{"display_login":"qiongsiwu"}}