[m-rev.] for review: added examples to mercury/extras/gator/README

[Julien Fischer]

On Thu, 16 Feb 2006, Samrith UONG wrote:

> On 2/15/06, Julien Fischer <juliensf at cs.mu.oz.au> wrote:
> >
> > On Wed, 15 Feb 2006, Samrith UONG wrote:
> > > +The new program is in "benchmarks/progs/ray/proj.m", rather than
> > > +"mercury/samples/hello.m".  The first thing that needs to be done is to
> > > +copy the program's source code to each of the hosts.
> >
> > One item that should be on the TODO list for this is to automate that
> > step.
>
> That's a good idea.
>
> > > +Suppose the evaluate.conf file (see section 3 for details) specifies two
> > > +programs, both of which are compiled with gcc(1).  In this case, the
> > > +first term would need to be a list of length $num_progs * 3 = 2 * 3 = 6.
> > > +The second term would need to contain a list of gcc optimisation
> > > +options, rather than mmc options.
> > > +
> > > +       [ 0.5, 0.5, 0.0, 0.0, 1.0, 1.0 ].
> > > +
> > > +       [ "-fbranch-probabilities", "-fcaller-saves", "-fcprop-registers" ].
> > > +
> >
> > I suggest adding a separate set of configuration files that show how to
> > optimise a simple C program with gcc as well.
>
> How about just adding all the gcc options in the README?  It's fairly
> long I suppose but not too hard to skip over.
>
> 	[ 0.5, 0.5, 0.0, 0.0, 1.0, 1.0 ].
>
> 	[ "-fbranch-probabilities", "-fcaller-saves",
> 	  "-fcprop-registers", "-fcse-follow-jumps",
> 	  "-fcse-skip-blocks", "-fdata-sections", "-fdelayed-branch",
> 	  "-fdelete-null-pointer-checks", "-fexpensive-optimizations",
> 	  "-ffast-math", "-ffloat-store", "-fforce-addr",
> 	  "-fforce-mem", "-ffunction-sections", "-fgcse", "-fgcse-lm",
> 	  "-fgcse-sm", "-floop-optimize", "-fcrossjumping",
> 	  "-fif-conversion", "-fif-conversion2", "-finline-functions",
> 	  "-fkeep-inline-functions", "-fkeep-static-consts",
> 	  "-fmerge-constants", "-fmerge-all-constants",
> 	  "-fmove-all-movables", "-fnew-ra", "-fno-branch-count-reg",
> 	  "-fno-default-inline", "-fno-defer-pop", "-fno-function-cse",
> 	  "-fno-guess-branch-probability", "-fno-inline",
> 	  "-fno-math-errno", "-fno-peephole", "-fno-peephole2",
> 	  "-funsafe-math-optimizations", "-ffinite-math-only",
> 	  "-fno-trapping-math", "-fno-zero-initialized-in-bss",
> 	  "-fomit-frame-pointer", "-foptimize-register-move",
> 	  "-foptimize-sibling-calls", "-fprefetch-loop-arrays",
> 	  "-freduce-all-givs", "-fregmove", "-frename-registers",
> 	  "-freorder-blocks", "-freorder-functions",
> 	  "-frerun-cse-after-loop", "-frerun-loop-opt",
> 	  "-fschedule-insns", "-fschedule-insns2",
> 	  "-fno-sched-interblock", "-fno-sched-spec",
> 	  "-fsched-spec-load", "-fsched-spec-load-dangerous",
> 	  "-fsignaling-nans", "-fsingle-precision-constant",
> 	  "-fssa", "-fssa-ccp", "-fssa-dce", "-fstrength-reduce",
> 	  "-fstrict-aliasing", "-ftracer", "-fthread-jumps",
> 	  "-funroll-all-loops", "-funroll-loops" ].
>

Fine, although there's probably not much need for all the options,
just a subset of them ought to suffice.  You may also want to mention
which version of gcc they belong to (since gcc options change with
versions of gcc).

Julien.
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------