From owner-freebsd-current@FreeBSD.ORG Thu Jan 27 11:49:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E228716A4CE; Thu, 27 Jan 2005 11:49:34 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C05243D49; Thu, 27 Jan 2005 11:49:29 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.19] (ibook-nai.samsco.home [192.168.254.19]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0RBqXgE006549; Thu, 27 Jan 2005 04:52:33 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <41F8D54F.9090802@samsco.org> Date: Thu, 27 Jan 2005 04:49:35 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Divacky Roman References: <20050127113906.GA98285@stud.fit.vutbr.cz> In-Reply-To: <20050127113906.GA98285@stud.fit.vutbr.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: scottl@freebsd.org cc: current@freebsd.org Subject: Re: recent current kernel compile failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 27 Jan 2005 11:49:35 -0000 Divacky Roman wrote: > hi > > recent current with CFLAGS=-O2: > > ../dev/amr/amr_pci.c > /usr/src/sys/modules/amr/../../dev/amr/amr_pci.c: In function `amr_setup_mbox': > /usr/src/sys/modules/amr/../../dev/amr/amr_pci.c:605: warning: dereferencing > type-punned pointer will break strict-aliasing rules > > would be nice to have this repaired > > roman We don't support compiling with -fstrict-aliasing. The correct solution is likely to change the type of 'p' and add a bunch of casts. Not very pretty, but I guess no worse than the horribly non-informative gcc message that is generated here. Scott