Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  Index 2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
<== Date ==> <== Thread ==>

Subject: Re: C strict aliasing rules
From: Benjamin Franksen <benjamin.franksen@bessy.de>
To: core-talk@aps.anl.gov
Date: Tue, 28 Nov 2006 02:20:38 +0100
Merely a side remark:

On Monday 27 November 2006 23:43, Eric Norum wrote:
> The writethree function doesn't even have to come first.  The
> optimizer appears to work on the file after it's all been consumed:
> ...

It would indeed be a poor optimizer if it wouldn't take all available 
data (=routines) into account. One may easily to do parsing in a 
strictly sequential manner, maybe even type checking (if the language 
is crippled enough to allow that), but optimizing? No way.

Cheers
Ben
PS: whatever happened to the notorious compiler warning 'xyz disables 
strict aliasing rules'? Seems to me as if compilers once were able to 
detect cases where the assumptions broke down. Hmmm.

Replies:
Re: C strict aliasing rules Eric Norum
References:
C strict aliasing rules Eric Norum
Re: C strict aliasing rules Andrew Johnson
Re: C strict aliasing rules Eric Norum

Navigate by Date:
Prev: Re: C strict aliasing rules Eric Norum
Next: Re: C strict aliasing rules Eric Norum
Index: 2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
Navigate by Thread:
Prev: Re: C strict aliasing rules Eric Norum
Next: Re: C strict aliasing rules Eric Norum
Index: 2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·