> | -fno-strict-aliasing in MD is acceptable compromise for me. > > Until that stops working, or being available. I think we should > let the majority decide what's appropriate.
if -fstrict-aliasing becomes the only option than we'll need a few years to clean up the kernel. ie, i don't think this is a real problem. what's appropriate is having something that works, and that the maintainers of the code accept. i tend to agree with christos about what would be the best, but i'm OK with tsutsui using an already heavily used flag to avoid a problem in code he maintains. i've often been unable to work on a port-sparc specific issue because some change was not well tested, so instead of advancing the state of the art, i'm stuck playing catch up all the time. i understand where he's coming from. .mrg.