Skip to content

Commit 3eeb717

Browse files
committed
Move some error flags to warnings
Appears to be a GCC bug causing `restrict` warnings, and some `maybe-uninitialized` ones that are more senstive. Downgrade them to warnings since getting the compiler upgraded is time-sensitive. Signed-off-by: Samuel E. Browne <[email protected]>
1 parent c10984b commit 3eeb717

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

cmake/ProjectCompilerPostConfig.cmake

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,10 +65,12 @@ set(upcoming_warnings
6565
array-bounds=2
6666
class-memaccess
6767
dangling-pointer=2
68+
maybe-uninitialized
6869
mismatched-new-delete
6970
overloaded-virtual=1
7071
pessimizing-move
7172
range-loop-construct
73+
restrict
7274
unused-but-set-variable
7375
uninitialized
7476
${Trilinos_ADDITIONAL_WARNINGS}
@@ -112,7 +114,6 @@ set(promoted_warnings
112114
int-to-pointer-cast
113115
logical-not-parentheses
114116
main
115-
maybe-uninitialized
116117
memset-elt-size
117118
memset-transposed-args
118119
misleading-indentation
@@ -127,7 +128,6 @@ set(promoted_warnings
127128
parentheses
128129
pointer-sign
129130
reorder
130-
restrict
131131
return-type
132132
self-move
133133
sequence-point

0 commit comments

Comments
 (0)