From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeffrey A Law <law@cygnus.com>
To: mrs@wrs.com (Mike Stump)
Cc: jbuck@Synopsys.COM, chip@perlsupport.com, craig@jcb-sc.com, davem@redhat.com, egcs@egcs.cygnus.com, mark@codesourcery.com, torvalds@transmeta.com
Subject: Re: Linux and aliasing? 
Date: Wed, 30 Jun 1999 15:43:00 -0000
Message-ID: <18698.928523295@upchuck.cygnus.com>
References: <199906041854.LAA05487@kankakee.wrs.com>
X-SW-Source: 1999-06n/msg00164.html
Message-ID: <19990630154300.UEsIOExlAkjjRiqEoUXVp39hrBXOO902cQttoyy8SD4@z>

  In message < 199906041854.LAA05487@kankakee.wrs.com >you write:

  > > In that case, then all release announcements and NEWS should prominently
  > > mention the effect of this new optimization and the -fno-strict-aliasing
  > > flag, so that everyone has fair warning.
  > 
  > I agree.  I am trying to figure out how to alert my entire company of
  > this new feature.  I am sure we have old networking code and tons of
  > programmers that probably aren't used to optimizing compilers.  :-)
I suspect you're not totally alone :-)    If you write up any kind of summary
with examples of dangerous code I think everyone would find it useful.  Any
chance you could post it so that we can put it on the web?

jeff