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

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
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:20:39
Message-ID: 87ftynu53e.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>>>>> "Andre" == Andre Mikulec <Andre_Mikulec(at)Hotmail(dot)com> writes:

Andre> It is an up-to-date compiler.

That doesn't mean it lacks bugs!

It's even TELLING YOU that it's an "internal compiler error". That means
the error is in the compiler, not in the code being compiled.

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

In a function that returns void, a missing return statement is
absolutely legal.

The SO question you linked to is irrelevant because that's talking about
a function that returns a value (not void).

--
Andrew (irc:RhodiumToad)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2018-09-05 19:23:46 Re: Bug: x86_64-w64-mingw32 REL_11_STABLE with features: UpdateStatisticsForTypeChange internal compiler error
Previous Message Andre_Mikulec 2018-09-05 19:12:19 Re: Bug: x86_64-w64-mingw32 REL_11_STABLE with features: UpdateStatisticsForTypeChange internal compiler error