That's a good point. Not all compilers use -O3 (for instance, that option would cause an error on Sun Studio.) So I guess it isn't really a good idea to modify the CFLAGS/CXXFLAGS in that manner. I will look into changing the default for post 1.0.0. I also need to quantify exactly how much boost I get from -O3 at the aggregate level.
Adam Tkac wrote: >> No, that just adds to the CFLAGS/CXXFLAGS defined implicitly by >> autoconf. Thus, I end up with 'cc -O2 -O3'. >> >> What I want is a way to change the implicit -O2 C flag based on whether >> or not a particular build condition is true. >> >> > > When you add "-Ox" flag to the end of current C*FLAGS the last option > is effective. It is true for GCC but I think other compilers have same > behavior. > > Adam > > ------------------------------------------------------------------------------ _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
