Another set of new gcc 4.6 warnings: readfuncs.c: In function ‘_readCaseWhen’: readfuncs.c:875:567: warning: variable ‘token’ set but not used [-Wunused-but-set-variable] readfuncs.c: In function ‘_readFromExpr’: readfuncs.c:1159:568: warning: variable ‘token’ set but not used [-Wunused-but-set-variable]
read.c: In function ‘nodeTokenType’: read.c:222:8: warning: variable ‘val’ set but not used [-Wunused-but-set-variable] I couldn't see a way good way of programming around this (perhaps in the second case, but it would get uselessly ugly), so perhaps just marking the variables as potentially unused would be appropriate? See patch.
diff --git i/src/backend/nodes/read.c w/src/backend/nodes/read.c index 78775e8..5c872e8 100644 --- i/src/backend/nodes/read.c +++ w/src/backend/nodes/read.c @@ -219,7 +219,7 @@ nodeTokenType(char *token, int length) * We know the token will end at a character that strtol will stop at, * so we do not need to modify the string. */ - long val; + long val __attribute__((unused)); char *endptr; errno = 0; diff --git i/src/backend/nodes/readfuncs.c w/src/backend/nodes/readfuncs.c index 2288514..4c9e98f 100644 --- i/src/backend/nodes/readfuncs.c +++ w/src/backend/nodes/readfuncs.c @@ -47,7 +47,7 @@ /* And a few guys need only the pg_strtok support fields */ #define READ_TEMP_LOCALS() \ - char *token; \ + char *token __attribute__((unused)); \ int length /* ... but most need both */
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
