My first concern with the -fast option is that it makes an executable
that is specific for the platform on which the compilation is run
unless other flags are given. My second concern is the effect it has
on IEEE floating point behavior w.r.t. rounding, error handling, ....
And my third concern is that if you use -fast, all other code must
be compiled and linked with the -fast option for correct operation,
this includes any functional languages such as perl, python, R,...
That is a pretty big requirement for a default compilation flag.

Ken Marshall

On Thu, Oct 09, 2003 at 12:07:20PM -0400, Jeff wrote:
> On Thu, 9 Oct 2003, Bruce Momjian wrote:
> > > 52 seconds to 19-20 seconds
> >
> > Wow, that's dramatic.  Do you want to propose some flags for non-gcc
> > Solaris?  Is -fast the only one?  Is there one that suppresses those
> > warnings or are they OK?
> >
> Well. As I said, I didn't see an obvious way to hide those warnings.
> I'd love to make those warnings go away.  That is why I suggested perhaps
> printing a message to ensure the user knows that warnings may be printed
> when using sunsoft.
> -fast should be all you need - it picks the "best settings" to use for the
> platform that is doing the compile.
> --
> Jeff Trout <[EMAIL PROTECTED]>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to