[PATCH] Removes uninitialized variable compiler warning

Started by Todd Sedanoover 9 years ago3 messageshackers
Beta feature

Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.

won't retrysuccessCI history

You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:

docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t36286
psql -h localhost -U postgres

Built from patchset v1 (message #1), July 28, 2026 at 07:46 AM.

Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:

git clone --branch t36286_1 https://github.com/hackorum-dev/postgres.git

In a checkout you already have, add the fork once:

git remote add hackorum https://github.com/hackorum-dev/postgres.git

then, for this patchset and every later one:

git fetch hackorum t36286_1 && git checkout t36286_1

Patchset v1 (message #1) is on t36286_1

Jump to latest
#1Todd Sedano
tsedano@pivotal.io

This patch removes a compiler warning.

warning: variable 'lenlemm' is uninitialized when used here
[-Wuninitialized]

This is my first commit to postgres. I've read through
http://wiki.postgresql.org/wiki/Submitting_a_Patch, but I may have missed
something.

diff --git a/src/backend/tsearch/ts_parse.c b/src/backend/tsearch/ts_parse.c
index b612fb0e2c..3d66b2babd 100644
--- a/src/backend/tsearch/ts_parse.c
+++ b/src/backend/tsearch/ts_parse.c
@@ -357,8 +357,8 @@ LexizeExec(LexizeData *ld, ParsedLex **correspondLexem)
 void
 parsetext(Oid cfgId, ParsedText *prs, char *buf, int buflen)
 {
-       int                     type,
-                               lenlemm;
+       int                     type;
+       int                     lenlemm = 0;
        char       *lemm = NULL;
        LexizeData      ldata;
        TSLexeme   *norms;

Attachments:

t36286_1
lenlemm_remove_compiler_warning.patchapplication/octet-stream; name=lenlemm_remove_compiler_warning.patchDownload+2-2
#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Todd Sedano (#1)
Re: [PATCH] Removes uninitialized variable compiler warning

Todd Sedano <tsedano@pivotal.io> writes:

This patch removes a compiler warning.
warning: variable 'lenlemm' is uninitialized when used here
[-Wuninitialized]

Hm, on what compiler? AFAICS, that parsetext() function hasn't
changed meaningfully since 2007, and nobody complained of
uninitialized-variable warnings in it before.

We're generally willing to try to silence such warnings on mainstream
compilers, but not on weird ones ...

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#3Todd Sedano
tsedano@pivotal.io
In reply to: Tom Lane (#2)
Re: [PATCH] Removes uninitialized variable compiler warning

We can disregard this patch. It appears that PointerGetDatum initializes
lenlemm.

On Mon, Mar 20, 2017 at 10:04 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Show quoted text

Todd Sedano <tsedano@pivotal.io> writes:

This patch removes a compiler warning.
warning: variable 'lenlemm' is uninitialized when used here
[-Wuninitialized]

Hm, on what compiler? AFAICS, that parsetext() function hasn't
changed meaningfully since 2007, and nobody complained of
uninitialized-variable warnings in it before.

We're generally willing to try to silence such warnings on mainstream
compilers, but not on weird ones ...

regards, tom lane