diff options
author | Jeremy Bettis <jbettis@google.com> | 2022-10-12 18:00:30 -0600 |
---|---|---|
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | 2022-10-13 17:12:59 +0000 |
commit | b6e08b63154cd9370f5206b7a3f928b44c31478d (patch) | |
tree | 584542d3bbd4641c8c9288dfabbf53e12881a718 | |
parent | ff6dcf2fd4532b609ff7c390d3dc799c77d0c0bc (diff) | |
download | chrome-ec-b6e08b63154cd9370f5206b7a3f928b44c31478d.tar.gz |
ec: Add #line directive to fix odd coverage.
Sometimes we get coverage reports where it appears that the coverage
data is all shifted off by one line, leaving many comments and blank
lines uncovered. For example see
http://goto.google.com/cros-ec-coverage/firmware-zephyr-cov-postsubmit/R108-15179.0.0-72225-8800548096768350721/lcov_rpt/common/keyboard_scan.c.gcov.html
In looking at that example, I discovered that for brya, in ro
only, when looking at the preprocessor output, the lines get shifted.
BRANCH=None
BUG=b:253131248
TEST=So many gcc -E runs
Signed-off-by: Jeremy Bettis <jbettis@google.com>
Change-Id: I6e852548cb954ed3ee3c47088ed275bc32892753
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3949582
Code-Coverage: Zoss <zoss-cl-coverage@prod.google.com>
Reviewed-by: Al Semjonovs <asemjonovs@google.com>
Tested-by: Jeremy Bettis <jbettis@chromium.org>
Auto-Submit: Jeremy Bettis <jbettis@chromium.org>
Commit-Queue: Al Semjonovs <asemjonovs@google.com>
-rw-r--r-- | include/chipset.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/chipset.h b/include/chipset.h index a3b3a94206..54c325639a 100644 --- a/include/chipset.h +++ b/include/chipset.h @@ -28,6 +28,7 @@ * approximating this state?" and not "Tell me what state the chipset is in and * I'll compare it myself with the state(s) I want." */ +#line 31 /* The comment above some how confuses the preprocessor. */ enum chipset_state_mask { CHIPSET_STATE_HARD_OFF = 0x01, /* Hard off (G3) */ CHIPSET_STATE_SOFT_OFF = 0x02, /* Soft off (S5, S4) */ |