Clemens Hammacher 2203a37c5d Replace CHECK(false) by UNREACHABLE() ... ... or sometimes by FATAL(...) to give a better error message. The benefit of UNREACHABLE() over CHECK(false) is that the compiler knows that this macro will never return, hence we can omit the return of a dummy value afterwards. R=neis@chromium.org Change-Id: I14e6a4f1d75f1338f481bd1520d841fd383d6202 Reviewed-on: https://chromium-review.googlesource.com/832431 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#50214}		2017-12-19 18:58:07 +00:00
..
live-range-unittest.cc	Move register allocation unittests and constrain owners	2016-12-17 00:24:36 +00:00
move-optimizer-unittest.cc	Replace CHECK(false) by UNREACHABLE()	2017-12-19 18:58:07 +00:00
OWNERS	Move register allocation unittests and constrain owners	2016-12-17 00:24:36 +00:00
register-allocator-unittest.cc	[iwyu|arm64] Pre-work for removing the illegal include macro-assembler.h -> assembler-inl.h	2017-03-15 12:08:50 +00:00