File: warn-conditional-emum-types-mismatch.c

package info (click to toggle)
llvm-toolchain-15 1%3A15.0.6-4
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,554,644 kB
  • sloc: cpp: 5,922,452; ansic: 1,012,136; asm: 674,362; python: 191,568; objc: 73,855; f90: 42,327; lisp: 31,913; pascal: 11,973; javascript: 10,144; sh: 9,421; perl: 7,447; ml: 5,527; awk: 3,523; makefile: 2,520; xml: 885; cs: 573; fortran: 567
file content (37 lines) | stat: -rw-r--r-- 920 bytes parent folder | download | duplicates (14) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
 
// RUN: %clang_cc1 -x c -fsyntax-only -verify -Wenum-compare-conditional %s
// RUN: %clang_cc1 -x c++ -fsyntax-only -verify -Wenum-compare-conditional %s

enum ro { A = 0x10 };
enum rw { B = 0xFF };
enum { C = 0x1A};

enum {
  STATUS_SUCCESS,
  STATUS_FAILURE,
  MAX_BASE_STATUS_CODE
};

enum ExtendedStatusCodes {
  STATUS_SOMETHING_INTERESTING = MAX_BASE_STATUS_CODE + 1000,
};


int get_flag(int cond) {
  return cond ? A : B; 
  #ifdef __cplusplus
  // expected-warning@-2 {{conditional expression between different enumeration types ('ro' and 'rw')}}
  #else 
  // expected-no-diagnostics
  #endif
}

// In the following cases we purposefully differ from GCC and dont warn because
// this code pattern is quite sensitive and we dont want to produce so many false positives.

int get_flag_anon_enum(int cond) {
  return cond ? A : C;
}

int foo(int c) {
  return c ? STATUS_SOMETHING_INTERESTING : STATUS_SUCCESS;
}