Skip to content

Commit 017551f

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. Same with `redundant-move`. Signed-off-by: Samuel E. Browne <[email protected]>
1 parent 3ffbec4 commit 017551f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

cmake/ProjectCompilerPostConfig.cmake

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,10 @@ 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+
redundant-move # -Wextra
73+
restrict
7174
#unused-parameter # -Wextra, lots of warnings
7275
${Trilinos_ADDITIONAL_WARNINGS}
7376
)
@@ -118,7 +121,6 @@ set(promoted_warnings
118121
int-to-pointer-cast
119122
logical-not-parentheses
120123
main
121-
maybe-uninitialized
122124
memset-elt-size
123125
memset-transposed-args
124126
misleading-indentation
@@ -136,9 +138,7 @@ set(promoted_warnings
136138
parentheses
137139
pointer-sign
138140
range-loop-construct
139-
redundant-move # -Wextra
140141
reorder
141-
restrict
142142
return-type
143143
self-move
144144
sequence-point

0 commit comments

Comments
 (0)