From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19393 invoked by alias); 16 Sep 2009 09:55:19 -0000 Received: (qmail 19138 invoked by alias); 16 Sep 2009 09:55:08 -0000 Date: Wed, 16 Sep 2009 09:55:00 -0000 Message-ID: <20090916095508.19136.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/41368] Erroneous aliasing rules violation messages are issued In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "yuri at rawbw dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-09/txt/msg01439.txt.bz2 ------- Comment #4 from yuri at rawbw dot com 2009-09-16 09:55 ------- Subject: Re: Erroneous aliasing rules violation messages are issued rguenth at gcc dot gnu dot org wrote: > ------- Comment #3 from rguenth at gcc dot gnu dot org 2009-09-16 08:02 ------- > The compiler warns for the store in > > D.1845_1 = (struct Fffff *) &eee.llll[0]; > D.1854_8 ={v} &0B->D.1740.rrrr[0]; > D.1845_1->ppp1 = D.1854_8; > > because that stores to eee.llll (type char) via a pointer to type Fffff which > is invalid. > > If this is the case, I agree with the warning, but why is it placed in function 'bbb', and not in 'ggg'? 'ggg' is the one that converts from unsigned char to Fffff. I believe this is a bug that message is misplaced. This makes message misleading and confusing. Message line should be fixed, and also it should be one message, not two. This case should be reopened. Thank you, Yuri -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41368