-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/04/11 10:00, Andrew MacLeod wrote: > On 11/04/2011 11:39 AM, Jeff Law wrote: >> On 11/03/11 17:49, Andrew MacLeod wrote: >>> This is the first of 2 parts for the patches to the GCC >>> directory, it includes the changelog for parts 1 and 2 >>> >>> Primarily it is all the stuff required to create builtins. new >>> defs, support routines, config changes, etc. It also includes >>> rth's 386 port to the new builtins. >>> >>> The second part contains the actual built-in code in >>> builtins.c and optabs.c. >> The only comment I've got on this patch is wondering why the -f >> options are PARAMS. >> >> I thought PARAMS were used more to tune along a range of values >> -- recursive depth for inlining, # iterations of certain passes, >> clamp number of items on lists, etc. >> >> Unless I'm missing something the new -f options have a range [01] >> and could just as easily have been -f<blah> -fno-<blah> >> options. >> >> Am I missing something? > Long drawn out discussion. It was -f initially, then it was > requested to be changed to -param, and every once in a while, > someone asks why it isn't -f :-) > > http://gcc.gnu.org/ml/gcc-patches/2011-07/msg02441.html :-) Works for me, just seemed a bit odd.
jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOtBqOAAoJEBRtltQi2kC7ZvgH/0keFp+a6zqeCfS0rVeWEEu4 VmFhgY7LPf3E0XqoORYMI4wOJIKQovGFnHpvxoVRFLc8xI5Z5wjY65nh5S5E5mej kK5vb4giTlph53Ea58MNUdaqFe72f4RBOznBO5AWoNrpWlnQRY44YkK5jK1CgpO+ CsUcOXuYyaZkTFOjHdyNiUJPV2sZo+qUo2Z5uslQWXQ8mVIP/M016qtM4MMYmptx nQtEqfZadYuKA5CMbH2fLpYihmg2+YJ6WDeFvZy3XM6WVKytdSdzYDpkHIZyf2SC 66YoUXaid7/1cGu1E6LVn/teVY6+zG/5YsBmAtdWMc2R0rPPiQ1aL1vcGUgi8O0= =3unW -----END PGP SIGNATURE-----
