From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Bogus reports from coverage.postgresql.org |
Date: | 2018-03-11 18:12:05 |
Message-ID: | 31446.1520791925@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Sun, Mar 11, 2018 at 6:58 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So if you're up2date on gcc, we might have material for a gcc bug report
>> here. I'll try to reproduce it on recent Fedora, and if so file something
>> at Red Hat.
> The current gcc version in debin stable is:
> mha(at)galvin:~$ gcc --version
> gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
Hm. The closest I'm going to be able to get on Red Hat distros is one of
f22/gcc.spec:%global gcc_version 5.3.1
f23/gcc.spec:%global gcc_version 5.3.1
f24/gcc.spec:%global gcc_version 6.3.1
f25/gcc.spec:%global gcc_version 6.4.1
f26/gcc.spec:%global gcc_version 7.3.1
f27/gcc.spec:%global gcc_version 7.3.1
f28/gcc.spec:%global gcc_version 8.0.1
I'll try this on 7.3.1, since I already have that on a handy laptop.
But if it doesn't reproduce there I think the answer is going to be
that Debian is shipping an old buggy gcov.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-03-11 19:03:20 | Re: Bogus reports from coverage.postgresql.org |
Previous Message | Magnus Hagander | 2018-03-11 18:02:29 | Re: Bogus reports from coverage.postgresql.org |