On Nov 28, 2006, at 9:50 AM, Kay-Uwe Kasemir wrote:
On Nov 28, 2006, at 10:37 , Eric Norum wrote:
The issue on the table is that of compilers imposing their strict
aliasing rules, and what to do about that.
For which we have to know where it all affects us:
- register access, I/O buffer encoding/decoding via mapped structures
- do-it-yourself inheritance from dbCommon to xyzRecord
What else?
I think that I/O buffer encoding/decoding via *any* cast, not just
via mapped structures might be at risk.
--
Eric Norum <[email protected]>
Advanced Photon Source
Argonne National Laboratory
(630) 252-4793
- Replies:
- Re: C strict aliasing rules Andrew Johnson
- References:
- C strict aliasing rules Eric Norum
- Re: C strict aliasing rules Benjamin Franksen
- Re: C strict aliasing rules Eric Norum
- Re: C strict aliasing rules Benjamin Franksen
- Re: C strict aliasing rules Kay-Uwe Kasemir
- Re: C strict aliasing rules Marty Kraimer
- Re: C strict aliasing rules Eric Norum
- Re: C strict aliasing rules Kay-Uwe Kasemir
- Navigate by Date:
- Prev:
Re: C strict aliasing rules Kay-Uwe Kasemir
- Next:
Re: C strict aliasing rules Andrew Johnson
- 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 Kay-Uwe Kasemir
- Next:
Re: C strict aliasing rules Andrew Johnson
- Index:
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|