On 12/09/03 John Nilsson wrote: > It was suggested in a discussion (bug[35184]) that this was files as a > > GLEP. This is just a quick dirty draft. Any comments would be > apreciated.
While it might be a good idea on the first view it has a number of problems: - the effect of -f and -O flags can be dependent on the hardware, e.g. -O3 creates bigger binaries that are faster than -O2 on a Xeon, but slower on a Duron or Celeron (due to different cache sizes). I'm sure this also applies to other flags. Further -O3 toggles different -f flags on different architectures (-fomit-frame-pointer on some non-x86 archs). - developer time: it would need an extreme amount of developer time to test all possible combinations for all C/C++ based packages, even if it's only done for new ebuilds. - user confusion: users will be very confused about this change when they CFLAGS don't work anymore (and allowing them to override them will negate most of the benefits of this proposal) - compatibility: each new gcc version has some new flags, so all these per-package flags would ahve to be revised as soon as there is a new gcc version out (with new version I mean the x or y in x.y.z). Marius -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better.
pgp00000.pgp
Description: PGP signature
