From owner-freebsd-tinderbox@FreeBSD.ORG Mon Jun 1 11:06:15 2009 Return-Path: Delivered-To: tinderbox@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09A721065672; Mon, 1 Jun 2009 11:06:15 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id AE0298FC08; Mon, 1 Jun 2009 11:06:14 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Subject:Message-ID:Reply-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender; b=QPfSHCiBtT33HhK9b9MXWplYCU+5vHAgrSB4a3JD8BZP4q103qdXhaNUwIEkpzt9X0b6xClLynUf8XprCJ5bkPtJcsTT8ppb8qc43nDyLyVzEHua9vkRYKKYJRaYAPmGp74btKLZpWVFRLqfqtDyLawXgzC5CRfoHAs2oPL7bUk=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1MB5LJ-000HzH-KU; Mon, 01 Jun 2009 15:06:13 +0400 Date: Mon, 1 Jun 2009 15:06:10 +0400 From: Eygene Ryabinkin To: Christoph Mallon Message-ID: References: <20090601042258.909C77302F@freebsd-current.sentex.ca> <4A2360BC.8040109@FreeBSD.org> <4A239B7C.8020403@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A239B7C.8020403@gmx.de> Sender: rea-fbsd@codelabs.ru Cc: FreeBSD Tinderbox , Doug Barton , current@freebsd.org, ia64@freebsd.org Subject: Re: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-tinderbox@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rea-fbsd@codelabs.ru List-Id: "Tinderbox reports, responses, and meta-comments" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2009 11:06:15 -0000 Christoph, good day. Mon, Jun 01, 2009 at 11:12:28AM +0200, Christoph Mallon wrote: > Eygene Ryabinkin schrieb: > > This is very weird (judging by the GCC's manual) since the simplest C > > program, > > ----- > > int main(void) > > { > > return 0; > > } > > > > void foo(void) __attribute__ ((unused)) > > { > > return; > > } > > ----- > > but ICC 10.x produces the same error and happily chewes __attribute__ > > on the function prototype. Anyway, I see no warnings even without > > '((unused)) attribute with -Wall, so '__attribute__ ((unused))' looks > > like no-op nowadays. > > There is no warning about foo() being unused, because it is not static. Yes, you're perfectly right. Thanks for education! -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ #