Re: BUG #15121: Multiple UBSAN errors
Martin Liška <marxin.liska@gmail.com>
From: Martin Liška <marxin.liska@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, pgsql-bugs@lists.postgresql.org
Date: 2018-03-19T20:01:28Z
Lists: pgsql-bugs
OK guys, you were right, it's miscompilation caused by GCC: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84969 Martin On 19 March 2018 at 20:18, Andres Freund <andres@anarazel.de> wrote: > On 2018-03-19 14:41:23 -0400, Tom Lane wrote: >> Andres Freund <andres@anarazel.de> writes: >> > On 2018-03-19 14:20:33 -0400, Tom Lane wrote: >> >> I tried -O3 with gcc 7.3.1 (Fedora 26), and that passes check-world >> >> just fine. Then I tried -O3 with gcc 8.0.1 (prerelease Fedora 28), >> >> and indeed that's got some problems. >> >> >> Note that 1-D and 2-D arrays print fine, it's only 3-D or deeper >> >> that print wrong. Very odd. Maybe it's bad code on our part, >> >> but I think the odds are at least as good that it's a new gcc bug. >> >> > Might be worth trying with a new clang, I think it's been a bit ahead on >> > the quality of the ubsan (et al) integration quality. >> >> I'm not talking about ubsan, I'm just talking about whether our regression >> tests pass with the higher -O level. > > Oh. I think I'll setup two BF animals that continually run using > debian's gcc-snapshot package, once with O0 and once with O3. > > Greetings, > > Andres Freund
Commits
-
Don't read fields of a misaligned ExpandedObjectHeader or AnyArrayType.
- b664b187d7ea 9.5.19 landed
- cd9d48969d94 10.10 landed
- 4b85f20f948d 11.5 landed
- 2938aa2a5b1c 9.6.15 landed
- 459c3cdb4ad8 12.0 landed
-
Doc: note that statement-level view triggers require an INSTEAD OF trigger.
- a46783204713 11.0 cited