Hello Martin,
The issue is resolved now and tests are fine for me.
I recompiled gcc trunk and the moonjelly is back to green.
Thanks!
--
Fabien.
Hello.
The issue is resolved now and tests are fine for me.
Martin
On Fri, 15 Nov 2019 at 13:11, Martin Liška wrote:
>
> Heh, it's me who now breaks postgresql build:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92529
>
> Martin
>
> On Fri, 15 Nov 2019 at 13:01, Fabien COELHO
> wrote:
> >
>
Heh, it's me who now breaks postgresql build:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92529
Martin
On Fri, 15 Nov 2019 at 13:01, Fabien COELHO
wrote:
>
>
> > Yes, after the revision I see other failing tests like:
>
> Indeed, I can confirm there are still 18/195 fails with the updated gcc.
Yes, after the revision I see other failing tests like:
...
select_having... ok 16 ms
subselect... FAILED 92 ms
union... FAILED 77 ms
case ... ok 32 ms
join
Yes, after the revision I see other failing tests like:
Indeed, I can confirm there are still 18/195 fails with the updated gcc.
I'm going to investigate that and will inform you guys.
Great, thanks!
--
Fabien.
Yep, I build periodically PostgreSQL package in openSUSE with the latest
GCC and so that I identified that and isolated to a simple test-case. I
would expect a fix today or tomorrow.
Indeed, the gcc issue reported seems fixed by gcc r278259. I'm updating
moonjelly gcc to check if this solve
Hi.
Yep, I build periodically PostgreSQL package in openSUSE with the
latest GCC and so
that I identified that and isolated to a simple test-case. I would expect a fix
today or tomorrow.
See you,
Martin
On Thu, 14 Nov 2019 at 16:46, Fabien COELHO wrote:
>
>
> Hello,
>
> I did a (slow) dichotomy
Hello,
I did a (slow) dichotomy on gcc sources which determined that gcc r277979
was the culprit, then I started a bug report which showed that the issue
was already reported this morning by Martin Liška, including a nice
example isolated from sources. See:
https://gcc.gnu.org/bugzi
so it sure looks like a gcc upgrade caused the failure. But it's not
clear wheter it's a compiler bug, or some undefined behaviour that
triggers the bug.
Fabien, any chance to either bisect or get a bit more information on
the backtrace?
There is a promising "keep_error_builds" option in bui
Hello Andres,
I don't think there's been any relevant code changes since the last
success.
last success:
2019-11-09 09:20:28.346 CET [28785:1] LOG: starting PostgreSQL 13devel on
x86_64-pc-linux-gnu, compiled by gcc (GCC) 10.0.0 20191102 (experimental),
64-bit
first failure:
2019-11-09 11
10 matches
Mail list logo
