Skip to content

Commit 5b60f7a

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 3ffbec4 commit 5b60f7a

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
@@ -67,7 +67,9 @@ set(upcoming_warnings
6767
dangling-pointer=2 # -Wall
6868
# deprecated-copy # -Wextra, lots of warnings
6969
implicit-fallthrough=3 # -Wextra
70+
maybe-uninitialized
7071
pessimizing-move # -Wall
72+
restrict
7173
#unused-parameter # -Wextra, lots of warnings
7274
${Trilinos_ADDITIONAL_WARNINGS}
7375
)
@@ -118,7 +120,6 @@ set(promoted_warnings
118120
int-to-pointer-cast
119121
logical-not-parentheses
120122
main
121-
maybe-uninitialized
122123
memset-elt-size
123124
memset-transposed-args
124125
misleading-indentation
@@ -138,7 +139,6 @@ set(promoted_warnings
138139
range-loop-construct
139140
redundant-move # -Wextra
140141
reorder
141-
restrict
142142
return-type
143143
self-move
144144
sequence-point

0 commit comments

Comments
 (0)