This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: dereferencing type-punned pointer will break strict-aliasing rules

From: Andrew Haley <aph at redhat dot com>
To: Jack Howarth <howarth at bromo dot msbb dot uc dot edu>
Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, Tom Tromey <tromey at redhat dot com>, java at gcc dot gnu dot org
Date: Fri, 13 Oct 2006 10:01:20 +0100
Subject: Re: dereferencing type-punned pointer will break strict-aliasing rules
References: <20061012230530.GA32232@bromo.msbb.uc.edu> <200610122306.k9CN6xV5008963@earth.phy.uc.edu> <20061012235537.GA32577@bromo.msbb.uc.edu>

Jack Howarth writes:
 > 
 > On Thu, Oct 12, 2006 at 07:06:59PM -0400, Andrew Pinski wrote:
 > > Because Andrew is saying that we need to change more than just
 > > where the warning is happening.

 >      What I actually meant was if these other cases also represent
 > aliasing violations that just happen not to be caught by the
 > compiler as warnings?

Please don't top-post.

I don't know if they generate warnings or not.  I do know that they
are aliasing violations.

Andrew.

References:
- Re: dereferencing type-punned pointer will break strict-aliasing rules
  - From: Jack Howarth
- Re: dereferencing type-punned pointer will break strict-aliasing rules
  - From: Andrew Pinski
- Re: dereferencing type-punned pointer will break strict-aliasing rules
  - From: Jack Howarth

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]