Derek Mauro 0320f517fd Work around a maybe-uninitialized warning under GCC 12 ... Some Mock constructors insert the pointer to the Mock itself into a global registry. Since GCC cannot see how the pointer is used (only as an identifier), it cannot tell that the object doesn't need to be initialized at that point at all. Work around this by using uintptr_t instead. PiperOrigin-RevId: 452380347 Change-Id: Ia5a493057ed90719de1d0efab71de9a8a08ddf8b		2022-06-01 14:08:04 -07:00
..
gmock_main.cc	Running clang-format over all of GoogleTest	2022-03-15 13:42:11 -07:00
gmock-all.cc	Comments changes, no functionality changes	2018-08-14 14:04:07 -04:00
gmock-cardinalities.cc	Remove the legacy internal GTEST_DISALLOW_* macros	2022-04-22 11:26:03 -07:00
gmock-internal-utils.cc	gmock-internal-utils.cc: Avoid implicit conversion from int to char	2022-05-17 01:37:27 -07:00
gmock-matchers.cc	Running clang-format over all of GoogleTest	2022-03-15 13:42:11 -07:00
gmock-spec-builders.cc	Work around a maybe-uninitialized warning under GCC 12	2022-06-01 14:08:04 -07:00
gmock.cc	Running clang-format over all of GoogleTest	2022-03-15 13:42:11 -07:00