Re: Fix runtime errors from -fsanitize=undefined - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Fix runtime errors from -fsanitize=undefined
Date
Msg-id 98a37944-6880-1c61-4aea-21fd0ba0b3bb@2ndquadrant.com
Whole thread Raw
In response to Re: Fix runtime errors from -fsanitize=undefined  (Noah Misch <noah@leadboat.com>)
Responses Re: Fix runtime errors from -fsanitize=undefined  (Raúl Marín Rodríguez <rmrodriguez@carto.com>)
Re: Fix runtime errors from -fsanitize=undefined  (Noah Misch <noah@leadboat.com>)
Re: Fix runtime errors from -fsanitize=undefined  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2019-07-05 01:33, Noah Misch wrote:
> I just saw this proposal.  The undefined behavior in question is strictly
> academic.  These changes do remove the need for new users to discover
> -fno-sanitize=nonnull-attribute, but they make the code longer and no clearer.
> Given the variety of code this touches, I expect future commits will
> reintroduce the complained-of usage patterns, prompting yet more commits to
> restore the invariant achieved here.  Hence, I'm -0 for this change.

This sanitizer has found real problems in the past.  By removing these
trivial issues we can then set up a build farm animal or similar to
automatically check for any new issues.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: mcvstats serialization code is still shy of a load
Next
From: Peter Eisentraut
Date:
Subject: Re: Add parallelism and glibc dependent only options to reindexdb