From owner-freebsd-current@FreeBSD.ORG Tue Mar 13 12:48:44 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C86C016A400; Tue, 13 Mar 2007 12:48:44 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 83CA713C44B; Tue, 13 Mar 2007 12:48:44 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1HR6Ql-000Pg6-7T; Tue, 13 Mar 2007 15:48:43 +0300 Date: Tue, 13 Mar 2007 15:48:36 +0300 From: Eygene Ryabinkin To: Andrey Chernov , current@freebsd.org Message-ID: <20070313124836.GV58523@codelabs.ru> References: <20070313121106.GA96293@nagual.pp.ru> <20070313123717.GU58523@codelabs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20070313123717.GU58523@codelabs.ru> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-2.1 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_50 Cc: Subject: Re: Bad gcc -O optimization cause core dump. What to do? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2007 12:48:44 -0000 > The ATTR_NOTHROW_NONNULL_1 makes me think that not all is lost and something > can be done with the NULL pointer. I am not very familiar with gcc > internals, but I will try to see if something can be changed. OK, the 'gcc -O -o test -fno-builtin-printf test.c' is your friend. -- Eygene