From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34351) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VnocF-0000fe-5M for qemu-devel@nongnu.org; Tue, 03 Dec 2013 06:58:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vnobi-0001d7-R2 for qemu-devel@nongnu.org; Tue, 03 Dec 2013 06:58:11 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53845) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vnobd-0001bp-6O for qemu-devel@nongnu.org; Tue, 03 Dec 2013 06:57:38 -0500 Message-ID: <529DC728.8050102@redhat.com> Date: Tue, 03 Dec 2013 12:57:28 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <87a9ginu92.fsf@blackfin.pond.sub.org> In-Reply-To: <87a9ginu92.fsf@blackfin.pond.sub.org> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH v1 0/5] Add error_abort and associated cleanups List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: imammedo@redhat.com, Peter Crosthwaite , qemu-devel@nongnu.org, afaerber@suse.de Il 03/12/2013 10:44, Markus Armbruster ha scritto: > > There are some _nofail functions left, but none of them can use > error_abort. > > If anything assigns to error_abort, we're probably screwed. No bright > idea how to prevent that at compile-time. Isn't it always used by address? Paolo