Re: BUG #16823: Unreachable code - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16823: Unreachable code
Date
Msg-id 1284342.1610556126@sss.pgh.pa.us
Whole thread Raw
In response to BUG #16823: Unreachable code  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16823: Unreachable code
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> localtime.c:135:40: warning: code will never be executed
> [-Wunreachable-code]
>                 result -= !TWOS_COMPLEMENT(int32) && result != 0;
>                                                      ^~~~~~

[ and much more in the same vein ]

We're unlikely to change any of these, so I'd recommend turning off
-Wunreachable-code.

localtime.c is a clone of the IANA timezone code, so we're certainly
not going to change it unless they do (which I doubt they would).
bootparse.c, and some of the other files you mention, are code generated
by bison, which we have no control over.  Most of the rest of these
are already manually commented as being unreachable; they're there
partly for belt-and-suspenders reasons, and partly because some other
compilers will warn if we don't have them.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16820: PG will have a deadlock when multiple rows are updated concurrently
Next
From: PG Bug reporting form
Date:
Subject: BUG #16824: Planner chooses poor path on query with Merge Join and pagination