On Tue, 2010-02-23 at 11:11 -0800, Jeremy Huddleston wrote: > On Feb 23, 2010, at 11:07, Keith Packard wrote: > > > On Tue, 23 Feb 2010 13:37:18 -0500, Gaetan Nadon > > <[email protected]> wrote: > > > >> This patch will ensure the xserver continues to suppress the > >> optimization, based on strict aliasing rules, after the option > >> is removed from $CWARNFLAGS. There is no change in the object > >> code produced. > > > > I don't think we need to allow any of the code in the X server to be > > 'optimized' in this fashion, so I don't see a need to allow for > > per-directory selection. > > It would be helpful if I had the option to remove this flag from > XQuartz. > >
Patch #1 is designed to maintain status-quo following the removal of -fno-strict-aliasing from CWARNFLAGS and does not require subsequent patches. It's a 'global' setting. Patch #2 is designed to maintain status-quo, but making it easy for various parts of the code to enable optimization if appropriate. It was later altered for XQuartz, which could have been done through a subsequent patch. The alternative to patch #2 is for components to append -fstrict-aliasing to override -fno-strict-aliasing.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ xorg-devel mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-devel
