> I just noticed this (from Ben) in the recent changelogs. While I > admit that the savings of "not optimizing vsmoother when most users > don't use it" probably vastly exceed the costs of running a > non-optimized vsmoother... wouldn't making --disable-vsmoother the > default be a better option? Then users can turn it on with > --enable-everything or --enable-vsmoother, and in that case we can > build it with full optimizations.
I don't think so. the #pragma is intel-specific, so it should unaffect you if you are using anything other than icc. plus, i'd rather not disable genuine features based on a bug in a single compiler. (If you note I actually increased the optimization level in general from -O2 to -O3, but added an icc pragma to disable optimization in that single translation unit.) ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
