Andres Freund <andres@2ndquadrant.com> wrote:
> On 2013-11-12 19:58:31 -0500, Jeffrey Walton wrote:
>> Here are Clang 3.3 findings regarding illegal shifts. The code
>> will be subject to removal by the compiler and optimizer (and
>> linker if LTO is used).
> Those all seem to be runtime errors, so they aren't likely to be
> removed by the compiler. That's not to say they shouldn't be
> looked at though.
Attached are the runtime errors I got from using the clang 3.4
sanitizer with make check-world. I poked around some web search
results and found that according to the C99 spec, these seemed to
be flagging non-portable code. I doubt that the issue impacts any
currently-supported platforms, which is why I set it aside until I
saw this thread; but it might some day affect the ability to
support some new platform.
These runtime tests can't be considered complete because the
sanitizer chose to crash things five times when it found things it
didn't like. What it disliked was not immediately clear to me, but
I'll attach those, too. Four of the five are identical for the
first 20 lines in the stack trace, with similarities for a few
lines past that. Also attached, FWIW.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
