Re: Bug: x86_64-w64-mingw32 REL_11_STABLE with features: UpdateStatisticsForTypeChange internal compiler error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andre_Mikulec <Andre_Mikulec(at)Hotmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug: x86_64-w64-mingw32 REL_11_STABLE with features: UpdateStatisticsForTypeChange internal compiler error
Date: 2018-09-05 19:23:46
Message-ID: 13118.1536175426@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andre_Mikulec <Andre_Mikulec(at)Hotmail(dot)com> writes:
> It is an up-to-date compiler.

Doesn't mean it has no bugs. It is in fact *telling you* it has a bug.

> These people here do not think that "a missing return statement" is a good
> idea.

If they can convince the C standards committee, then I'll worry about
their opinion. Functions returning void are not required to have return
statements per the standard.

Moreover, I'm pretty sure this is not the only function in PG with an
empty body. I think the fact that the compiler is crashing right there
is likely not related to the empty function as such, but has a lot to do
with what else it has processed in the same compilation.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andre_Mikulec 2018-09-06 03:23:20 Re: Bug: x86_64-w64-mingw32 REL_11_STABLE with features: UpdateStatisticsForTypeChange internal compiler error
Previous Message Andrew Gierth 2018-09-05 19:20:39 Re: Bug: x86_64-w64-mingw32 REL_11_STABLE with features: UpdateStatisticsForTypeChange internal compiler error