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
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: C strict aliasing rules Eric Norum
- Next:
Re: C strict aliasing rules Eric Norum
- Index:
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|