| commit | 0af32302bb5b144739e7200c1678d6dcace50f12 | [log] [tgz] |
|---|---|---|
| author | jfb <jfb@chromium.org> | Thu Apr 07 05:20:31 2016 +0900 |
| committer | Qijiang Fan <fqj@google.com> | Fri Jun 05 02:54:35 2020 +0900 |
| tree | 1cd1c953bda72e04b0410bfb3ce2c9cecf91cc23 | |
| parent | 60985a5a8a8a6b1ff475b775d65cefddad481d49 [diff] |
Define HAS_FEATURE instead of __has_feature As discussed in: https://codereview.chromium.org/1837563002/ The approach is what's recommended by clang and is safe because __has_feature was only defined if the compiler didn't provide it, but nonetheless it's good to be consistent. R=thakis@chromium.org Review URL: https://codereview.chromium.org/1866473002 Cr-Commit-Position: refs/heads/master@{#385541} CrOS-Libchrome-Original-Commit: a8dc9dd8ca283435a6a312918f0526300c91e8de