pirama added a comment. From the discussion, it seems it is theoretically feasible to make optimization for speed a function-level attribute as well. After looking at the PassMangerBuilder for this bug, I think that'll make the optimization passes cleaner by keeping the passes and their behavior at various levels in one place.
Circling back to the issue at hand, what is the best way to handle Os and Oz at the lto stage? I think we left off with @mehdi_amini's comment that the driver should emit a warning when dropping the Os/Oz. https://reviews.llvm.org/D30920 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits