Skip to content

Commit 289ef38

Browse files
committed
Silence another gcc 11 warning.
Per buildfarm and local experimentation, bleeding-edge gcc isn't convinced that the MemSet in reorder_function_arguments() is safe. Shut it up by adding an explicit check that pronargs isn't negative, and by changing MemSet to memset. (It appears that either change is enough to quiet the warning at -O2, but let's do both to be sure.)
1 parent 6f94531 commit 289ef38

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/backend/optimizer/util/clauses.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4304,9 +4304,9 @@ reorder_function_arguments(List *args, HeapTuple func_tuple)
43044304
int i;
43054305

43064306
Assert(nargsprovided <= pronargs);
4307-
if (pronargs > FUNC_MAX_ARGS)
4307+
if (pronargs < 0 || pronargs > FUNC_MAX_ARGS)
43084308
elog(ERROR, "too many function arguments");
4309-
MemSet(argarray, 0, pronargs * sizeof(Node *));
4309+
memset(argarray, 0, pronargs * sizeof(Node *));
43104310

43114311
/* Deconstruct the argument list into an array indexed by argnumber */
43124312
i = 0;

0 commit comments

Comments
 (0)