{"push_id":2320679835,"size":117,"distinct_size":117,"ref":"refs/heads/master","head":"b8723a6345d70955265e27e6e9109f00aaad97e7","before":"2eec379b9b59bd859cb149d56fbb48041ca5a557","commits":[{"sha":"ea016449cc09bda656bc2b3ad643365b307df8dd","author":{"name":"George Karpenkov","email":"e5a62f38b9ed35f7669e7309c66bbc5e87a46557@apple.com"},"message":"[analyzer] [tests] Show the number of removed/added bug reports\n\nDifferential Revision: https://reviews.llvm.org/D42718\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@323941 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/ea016449cc09bda656bc2b3ad643365b307df8dd"},{"sha":"2cbd32574f151cbd67c1644b67f1cf7eea3fc18d","author":{"name":"Akira Hatanaka","email":"9b0cf1190e34e4dab0e0e0463e917e57d98208cb@apple.com"},"message":"[CodeGen] Fix an assertion failure in CGRecordLowering.\n\nThis patch fixes a bug in CGRecordLowering::accumulateBitFields where it\nunconditionally starts a new run and emits a storage field when it sees\na zero-sized bitfield, which causes an assertion in insertPadding to\nfail when -fno-bitfield-type-align is used.\n\nIt shouldn't emit new storage if UseZeroLengthBitfieldAlignment and\nUseBitFieldTypeAlignment are both false.\n\nrdar://problem/36762205\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@323943 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/2cbd32574f151cbd67c1644b67f1cf7eea3fc18d"},{"sha":"835a31e2eff12ee909b131e07a44e0b8558d801a","author":{"name":"Sander de Smalen","email":"715d8879f2ffe09f813020108dc164740f5cf013@arm.com"},"message":"[DebugInfo] Enable debug information for C99 VLA types\n\nSummary:\nThis patch enables debugging of C99 VLA types by generating more precise\nLLVM Debug metadata, using the extended DISubrange 'count' field that\ntakes a DIVariable.\n    \nThis should implement:\n  Bug 30553: Debug info generated for arrays is not what GDB expects (not as good as GCC's)\nhttps://bugs.llvm.org/show_bug.cgi?id=30553\n\nReviewers: echristo, aprantl, dexonsmith, clayborg, pcc, kristof.beyls, dblaikie\n\nReviewed By: aprantl\n\nSubscribers: jholewinski, schweitz, davide, fhahn, JDevlieghere, cfe-commits\n\nDifferential Revision: https://reviews.llvm.org/D41698\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@323952 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/835a31e2eff12ee909b131e07a44e0b8558d801a"},{"sha":"294a4f68ffd3bfbd9cde07f3c0b37f37077c66c5","author":{"name":"Sander de Smalen","email":"715d8879f2ffe09f813020108dc164740f5cf013@arm.com"},"message":"Reverting patch rL323952 due to build errors that I\nhaven't encountered in local builds.\n\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@323956 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/294a4f68ffd3bfbd9cde07f3c0b37f37077c66c5"},{"sha":"604238e317775b3ac1c6f1ccb0b53f404501c442","author":{"name":"Adrian Prantl","email":"3b76fbf1c74594027f839a53c333f1ac0d409492@apple.com"},"message":"Mark fallthrough with LLVM_FALLTHROUGH\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@323986 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/604238e317775b3ac1c6f1ccb0b53f404501c442"},{"sha":"f61575826a1eef7d0c0198d6f444894ec72ea394","author":{"name":"Richard Smith","email":"623b07eec604b9e26cffdaff9133eaf2c80f18f3@metafoo.co.uk"},"message":"PR36157: When injecting an implicit function declaration in C89, find the right\nDeclContext rather than injecting it wherever we happen to be.\n\nThis avoids creating functions whose DeclContext is a struct or similar.\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@323998 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/f61575826a1eef7d0c0198d6f444894ec72ea394"},{"sha":"7a8e626f21921c75c04088c8ec0874c668256ade","author":{"name":"Artem Dergachev","email":"9c257a9f5889b207f966593fb6de1d6fc101973e@gmail.com"},"message":"[analyzer] Don't communicate evaluation failures through memregion hierarchy.\n\nWe use CXXTempObjectRegion exclusively as a bailout value for construction\ntargets when we are unable to find the correct construction region.\nSometimes it works correctly, but rather accidentally than intentionally.\n\nNow that we want to increase the amount of situations where it works correctly,\nthe first step is to introduce a different way of communicating our failure\nto find the correct construction region. EvalCallOptions are introduced\nfor this purpose.\n\nFor now EvalCallOptions are communicating two kinds of problems:\n- We have been completely unable to find the correct construction site.\n- We have found the construction site correctly, and there's more than one of\n  them (i.e. array construction which we currently don't support).\n\nAccidentally find and fix a test in which the new approach to communicating\nfailures produces better results.\n\nDifferential Revision: https://reviews.llvm.org/D42457\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324018 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/7a8e626f21921c75c04088c8ec0874c668256ade"},{"sha":"ef79198e6867277f2d59ab16d601cec58b084164","author":{"name":"George Karpenkov","email":"e5a62f38b9ed35f7669e7309c66bbc5e87a46557@apple.com"},"message":"[analyzer] [tests] Add an option to show the histogram of path differences between the analyzer runs\n\nDifferential Revision: https://reviews.llvm.org/D42778\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324021 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/ef79198e6867277f2d59ab16d601cec58b084164"},{"sha":"de212366a3b025425ef488b469f40125a1c61549","author":{"name":"George Karpenkov","email":"e5a62f38b9ed35f7669e7309c66bbc5e87a46557@apple.com"},"message":"[analyzer] [tests] [NFC] Remove dead code from CmpRuns\n\nIndeed, \"CHANGE\" is not a thing yet, and we should probably not carry\naround dead code which does not do anything apart from confusing the\nreader.\n\nDifferential Revision: https://reviews.llvm.org/D42819\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324027 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/de212366a3b025425ef488b469f40125a1c61549"},{"sha":"5fb3bb840451f64825c8c310b7a22ac84740667d","author":{"name":"Eric Fiselier","email":"a16fbdd223a71781803acbd9bd107ba1353fc2f0@efcs.ca"},"message":"[coroutines] Fix application of NRVO to Coroutine \"Gro\" or return object.\n\nSummary:\nFix NRVO for Gro variable.\n\nPreviously, we only marked the GRO declaration as an NRVO variable\nwhen its QualType and the function return's QualType matched exactly\n(using operator==). However, this was incorrect for two reasons:\n\n1. We were marking non-class types, such as ints, as being NRVO variables.\n\n2. We failed to  handle cases where the canonical types were the same, but the actual `QualType` objects were different. For example, if  one was represented by a typedef. (Example: https://godbolt.org/g/3UFgsL)\n\nThis patch fixes these bugs by marking the Gro variable as supporting NRVO only\nwhen `BuildReturnStmt` marks the Gro variable as a coroutine candidate.\n\n\n\n\n\n\nReviewers: rsmith, GorNishanov, nicholas\n\nReviewed By: GorNishanov\n\nSubscribers: majnemer, cfe-commits\n\nDifferential Revision: https://reviews.llvm.org/D42343\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324037 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/5fb3bb840451f64825c8c310b7a22ac84740667d"},{"sha":"7806f274e20e3d9f0fbf4a0ffe2d1f1c3ccc5cce","author":{"name":"George Karpenkov","email":"e5a62f38b9ed35f7669e7309c66bbc5e87a46557@apple.com"},"message":"[analyzer] Fix yet-another-crash in body-farming std::call_once\n\nCrash occurs when parameters to the callback and to std::call_once\nmismatch, and C++ is supposed to auto-construct an argument.\n\nFiled by Alexander Kornienko in\nhttps://bugs.llvm.org/show_bug.cgi?id=36149\n\nrdar://37034403\n\nDifferential Revision: https://reviews.llvm.org/D42777\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324046 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/7806f274e20e3d9f0fbf4a0ffe2d1f1c3ccc5cce"},{"sha":"63f1a460027e2aec2f16562a76003202ae03ea25","author":{"name":"George Karpenkov","email":"e5a62f38b9ed35f7669e7309c66bbc5e87a46557@apple.com"},"message":"[analyzer] Expose exploration strategy through analyzer options.\n\nDifferential Revision: https://reviews.llvm.org/D42774\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324049 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/63f1a460027e2aec2f16562a76003202ae03ea25"},{"sha":"2794a6b57007336f5178ccce6cb06ad60093c919","author":{"name":"George Karpenkov","email":"e5a62f38b9ed35f7669e7309c66bbc5e87a46557@apple.com"},"message":"Remove the change which accidentally crept in into the cherry-pick\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324050 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/2794a6b57007336f5178ccce6cb06ad60093c919"},{"sha":"5885c75b8cfb19ed8ab6b4b7c4cec8fc5207cf13","author":{"name":"George Karpenkov","email":"e5a62f38b9ed35f7669e7309c66bbc5e87a46557@apple.com"},"message":"[analyzer] Expose return statement from CallExit program point\n\nIf the return statement is stored, we might as well allow querying\nagainst it.\nAlso fix the bug where the return statement is not stored\nif there is no return value.\nThis change un-merges two ExplodedNodes during call exit when the state\nis otherwise identical - the CallExitBegin node itself and the \"Bind\nReturn Value\"-tagged node.\nAnd expose the return statement through\ngetStatement helper function.\n\nDifferential Revision: https://reviews.llvm.org/D42130\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324052 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/5885c75b8cfb19ed8ab6b4b7c4cec8fc5207cf13"},{"sha":"cd369d49a2ea70390c28d51f391f00f57195738b","author":{"name":"Artem Dergachev","email":"9c257a9f5889b207f966593fb6de1d6fc101973e@gmail.com"},"message":"[analyzer] Fix transitions in check::PreStmt<MemberExpr> checker callback.\n\nNo in-tree checkers use this callback so far, hence no tests. But better fix\nthis now than remember to fix this when the checkers actually appear.\n\nPatch by Henry Wong!\n\nDifferential Revision: https://reviews.llvm.org/D42785\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324053 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/cd369d49a2ea70390c28d51f391f00f57195738b"},{"sha":"08712fff7fba84b88e2e57b3c739d53b1aab1ed6","author":{"name":"Martin Storsjo","email":"ea98e1d0a9a4d10e3af04e16be88050749615623@martin.st"},"message":"[MinGW] Emit typeinfo locally for dllimported classes without key functions\n\nThis fixes building Qt as shared libraries with clang in MinGW\nmode; previously subclasses of the QObjectData class (in other\nDLLs than the base DLL) failed to find the typeinfo symbols\n(that neither were emitted in the base DLL nor in the DLL\ncontaining the subclass).\n\nIf the virtual destructor in the newly added testcase wouldn't\nbe pure (or if there'd be another non-pure virtual method),\nit'd be a key function and things would work out even before this\nchange. Make sure to locally emit the typeinfo for these classes\nas well.\n\nThis matches what GCC does in this specific testcase.\n\nThis fixes the root issue that spawned PR35146. (The difference\nto GCC that is initially described in that bug still is present\nthough.)\n\nDifferential Revision: https://reviews.llvm.org/D42641\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324059 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/08712fff7fba84b88e2e57b3c739d53b1aab1ed6"},{"sha":"a2ca4ae98b35d76b14cc936af1ebf13b93199d79","author":{"name":"Ilya Biryukov","email":"658e01dc67dbff791f5efc53553965889ddf88ac@google.com"},"message":"[Sema] Add implicit members even for invalid CXXRecordDecls\n\nSummary:\nIt should be safe, since other code paths are already generating\nimplicit members even in invalid CXXRecordDecls (e.g. lookup).\n\nIf we don't generate implicit members on CXXRecordDecl's completion,\nthey will be generated by next lookup of constructors. This causes a\ncrash when the following conditions are met:\n  - a CXXRecordDecl is invalid,\n  - it is provided via ExternalASTSource (e.g. from PCH),\n  - it has inherited constructors (they create ShadowDecls),\n  - lookup of its constructors was not run before ASTWriter serialized\n    it.\n\nThis may require the ShadowDecls created for inherited constructors to\nbe removed from the class, but that's no longer possible since class is\nprovided by ExternalASTSource.\n\nSee provided lit test for an example.\n\nReviewers: bkramer\n\nReviewed By: bkramer\n\nSubscribers: cfe-commits\n\nDifferential Revision: https://reviews.llvm.org/D42810\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324062 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/a2ca4ae98b35d76b14cc936af1ebf13b93199d79"},{"sha":"e705029e94d188e30987bf3154b69a8a57aee3f1","author":{"name":"Sam McCall","email":"f6dc93ad0485e1598ac605961f5d4a81b04aad9e@gmail.com"},"message":"[AST] namespace ns { extern \"C\" { int X; }} prints as \"ns::X\", not as \"X\"\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324081 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/e705029e94d188e30987bf3154b69a8a57aee3f1"},{"sha":"7d84cfa2cd0b45ec41c08ffb9ae3ba56904a4a25","author":{"name":"Sam McCall","email":"f6dc93ad0485e1598ac605961f5d4a81b04aad9e@gmail.com"},"message":"[Index] fix USR generation for namespace{extern{X}}\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324093 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/7d84cfa2cd0b45ec41c08ffb9ae3ba56904a4a25"},{"sha":"b30dcee6c976abb67f887718f1900edb3351a1e5","author":{"name":"Erich Keane","email":"009897bb9192cd7d26ddf604877d3c678767b41e@intel.com"},"message":"[CodeGen][va_args] Correct Vector Struct va-arg 'in_reg' code gen\n\nWhen trying to track down a different bug, we discovered\nthat calling __builtin_va_arg on a vec3f type caused\nthe SROA pass to issue a warning that there was an illegal\naccess.\n\nFurther research showed that the vec3f type is\nalloca'ed as size '12', but the _builtin_va_arg code\non x86_64 was always loading this out of registers as\n{double, double}. Thus, the 2nd store into the vec3f\nwas storing in bytes 12-15!\n\nThis patch alters the original implementation which always\nassumed {double, double} to use the actual coerced type\ninstead, so the LLVM-IR generated is a load/GEP/store of\na <2 x float> and a float, rather than a double and a double.\n\nTests were added for all combinations I could think of that\nwould fit in 2 FP registers, and all work exactly as expected.\n\nDifferential Revision: https://reviews.llvm.org/D42811\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324098 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/schweitzpgi/flang-driver/commits/b30dcee6c976abb67f887718f1900edb3351a1e5"}]}
{"actor":{"display_login":"schweitzpgi"}}