From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============8284245081319657788==" MIME-Version: 1.0 From: Mark Wielaard To: elfutils-devel@lists.fedorahosted.org Subject: Re: [PATCH] configure: Add --enable-sanitize-undefined. Date: Wed, 27 May 2015 15:13:43 +0200 Message-ID: <1432732423.4538.125.camel@bordewijk.wildebeest.org> In-Reply-To: 1432244211-19438-1-git-send-email-mjw@redhat.com --===============8284245081319657788== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Thu, 2015-05-21 at 23:36 +0200, Mark Wielaard wrote: > Now that we are -fsanitize=3Dundefined clean make sure we keep it that wa= y. > = > We do have to disable alignment checking. Because we might explicitly > use unaligned accesses (see ALLOW_UNALIGNED). And we have to disable > integer overflow checking when running the tests under valgrind. Because > those are unreliable under VEX emulation. Turned out that was a bug in valgrind now fixed: https://bugs.kde.org/show_bug.cgi?id=3D348247 Luckily that bug never made it into a released valgrind version. I have pushed this change to master without the disabling of integer overflow checking under valgrind. Cheers, Mark --===============8284245081319657788==--