Fix non-clang build failure around STACK_ALLOCATED macro
STACK_ALLOCATED macro leaves `private:` section on clang build after https://crrev.com/c/1160424, and doesn't change the access specifier on non-clang build, that seems to confuse non-clang build. This CL unifies the difference to fix the non-clang build. Change-Id: I0fdd1236670a5dd64892c19fa642dd4d681e4008 Reviewed-on: https://chromium-review.googlesource.com/1164156Reviewed-by:Kentaro Hara <haraken@chromium.org> Commit-Queue: Taiju Tsuiki <tzik@chromium.org> Cr-Commit-Position: refs/heads/master@{#581144}
Showing
Please register or sign in to comment