Hi! > I'm concerned that the net performance gain here is going to be far > outweighed by the maintenance costs and user complexity. Without actually > measuring the gains, there's no guarantee that these changes will actually > improve performance, and in moving away from the optimization flags et al > selected by the original developers, could very possibly trigger bugs in code > generation output (e.g., compiler bugs, especially with bleeding-edge clang), > or reveal bugs in the project that aren't apparent at lower optimization > levels.
Well, clang-3.3 is, in principle, well known and (almost) bug free. It’s a full release version, not a bleeding edge compiler anymore… as for bugs in the project… well… they will have to be unearthed sooner or later anyhow. Remember that the perf variant is going to be optional anyhow, so we could easily restrict its use to the most advanced users. Vincent _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
