From owner-freebsd-current@FreeBSD.ORG  Sun Dec  1 02:20:47 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id DDBC0780
 for <current@freebsd.org>; Sun,  1 Dec 2013 02:20:47 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 76BEA18C5
 for <current@freebsd.org>; Sun,  1 Dec 2013 02:20:47 +0000 (UTC)
Received: from [157.181.98.186] ([157.181.98.186]) by mail.gmx.com (mrgmx103)
 with ESMTPSA (Nemesis) id 0LpKY5-1VAZ1Z0qur-00f9NB for
 <current@freebsd.org>; Sun, 01 Dec 2013 03:20:40 +0100
Message-ID: <529A9CD7.8080503@gmx.com>
Date: Sun, 01 Dec 2013 03:20:07 +0100
From: dt71@gmx.com
User-Agent: Mozilla/5.0 (X11; FreeBSD i386;
 rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20
MIME-Version: 1.0
To: Adrian Chadd <adrian@freebsd.org>, Dimitry Andric <dim@freebsd.org>
Subject: Re: RFC: (Unconditionally) enable -fno-strict-overflow for kernel
 builds
References: <20131130135616.GA59496@kib.kiev.ua>
 <E3E2524B-4423-4962-BFD7-9A81424296F7@FreeBSD.org>
 <CAJ-VmonQip5Q+DfSd_dba_=g8bZYM9uyhYw8XmhU4wGydnJJtg@mail.gmail.com>
In-Reply-To: <CAJ-VmonQip5Q+DfSd_dba_=g8bZYM9uyhYw8XmhU4wGydnJJtg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:TgkTlNeCGiSqNoUSajKmca5QCyeHV82A89mo2Z3cmTvjU1GMTjc
 gbcojAenZ/TEHVQ0IoEEDdKuWJ9NKDZMH7HZHVhv2f84e8Y7F44YwQAjBaomFSkeTS+yYZk
 OkYySFV32JY9iMczz2Kz7s2Y+vfBmbsEZJ+WKKlGjYx4pGI8XwJKUD8rS2bmt0zbtA9+ij6
 HhrhsH1/BuoaeLxT49mNQ==
Cc: Konstantin Belousov <kostikbel@gmail.com>,
 "current@freebsd.org" <current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Dec 2013 02:20:47 -0000

Adrian Chadd wrote, On 12/01/2013 01:33:
> Are you able to have clang/llvm/gcc tell us where/when code is relying
> on undefined behaviour? So we can, like, fix them?

Well, there's -ftrapv.