You did a great job Robin. I think as it stands now the program really provides a nice set of best-case scenario flags (Which is what I prefer most). If in the future you extend it to include experimental more strict optimizations, great, but as it stands now I like it. Thanks for providing this to us.

As far as the names go, I think you made the right call... I was just looking for something like "genflags" when I first emerged the package. Maybe a wrapper script by that name could list off the included executables and what they do?

Best,
-Riyad

Robin H.Johnson wrote:

On Tue, Aug 05, 2003 at 05:04:18PM -0700, Riyad Kalla wrote:

They might be referring to the genflags package, it comes with
strangely names info2flags, info2host and host2flags. It parses your
machine information and spits back safe/fast flags for you. Kind of a
middle ground. Not freakishly optimized, but also not going to cause
you to segfault at strange times.

I originally put out a call for better names, but nothing was suggested, so I stuck with the original names that describe what each script actually does. info2host - convert information to a reliable host identifier host2flags - generate flags information for a given host identifier info2flags - combine the above two for ease of use.


An example from a run-of-the-mill P4 Dell machine:

The application was initial written to support as many completely different architectures as possible, even stuff that gcc/binutils/kernel consider experimental like SH10 and Cris. The application will work reasonably well on practically any platform as a result of this.



--
[EMAIL PROTECTED] mailing list



Reply via email to