Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit22f71a6

Browse files
committed
Silence another gcc 11 warning.
Per buildfarm and local experimentation, bleeding-edge gcc isn'tconvinced 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 isenough to quiet the warning at -O2, but let's do both to be sure.)
1 parent7c53a80 commit22f71a6

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
@@ -4104,9 +4104,9 @@ reorder_function_arguments(List *args, HeapTuple func_tuple)
41044104
inti;
41054105

41064106
Assert(nargsprovided <=pronargs);
4107-
if (pronargs>FUNC_MAX_ARGS)
4107+
if (pronargs<0||pronargs>FUNC_MAX_ARGS)
41084108
elog(ERROR,"too many function arguments");
4109-
MemSet(argarray,0,pronargs*sizeof(Node*));
4109+
memset(argarray,0,pronargs*sizeof(Node*));
41104110

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

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp