On 3/18/10 3:47 PM, Carl-Daniel Hailfinger wrote: > On 18.03.2010 15:05, Stefan Reinauer wrote: > >> On 3/18/10 11:35 AM, Mark Marshall wrote: >> >> >>> This will mean that you've got wrong debug info, of course, but it is >>> what you seem to want. The first file defines a symbol, and the second >>> files says that a symbol is defined somewhere else. The types don't >>> match, but the C compiler doesn't know / care about that. >>> >>> >> Since the type punning issue is about wrong alignment, I think the C >> compiler does not do the right thing in that case, we just trick it >> around the warning. >> >> > AFAIK (and I could be wrong) type punning is not only about alignment, > but the C compiler is free to optimize the generated code in a way that > may break your expectations if you're violating strict aliasing rules. > > That's what I read over and over, too but I can't make much sense of it... what does it mean? What are we not supposed to expect? What is it about, more than alignment?
-- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
