>>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jul 3, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>> I think it might be a good idea to add the -pipe option to the
>> default CFLAGS if gcc is detected and the -pipe option is
>> supported. What do you think?
Alexandre> I think this should not be done by default. -pipe is more
Alexandre> CPU-intensive than regular builds, so it should be up to
Alexandre> the builder to decide whether to use it or not. -pipe may
Alexandre> work fine on a developer's high-end system, but not on Joe
Alexandre> User's low-end machine, nor in Joe Power User's case of
Alexandre> building with `make -j8' to make use of his SMP machine.
Alexandre> However, since there's demand for such a macro, we could
Alexandre> supply one that would refrain from adding -pipe, even if
Alexandre> supported, when a configure option such as --disable-pipe
Alexandre> is given. But IMHO this macro should not be used by
Alexandre> default; it's only for those developers that *think* they
Alexandre> know better than their users, and we should make it clear
Alexandre> in the docs that this macro is not recommended in general.
Precisely for these reasons, I don't think such a macro is needed, it
is not right. -pipe etc. should be under the control of the people
who will run configure, so it must not depend upon a decision from the
maintainer. I would not be happy with an extra macro. Either all the
configures do that, or none.
Still, personally I find that such configure-time optimizations fall
under the config.site rule.
