              The SUIF Frequently Asked Questions List
              ========================================

  1. Q: ``The Makefile is broken.  What does, `Must be a separator on
        rules line 5.  Stop.' mean?''
     A: It means you're not using GNU make.  Try ``gmake'' instead.
        If gmake isn't in your path, find out where it's installed on
        your system and put it in your path.  If gmake isn't
        installed, you'll need to install it.  See the SUIF README
        file.

  2. Q: ``I compile the SPEC benchmark tomcatv (or some other large
        FORTRAN program) with SUIF and the compilation seems to work,
        but when I run the resulting binary it seg faults immediately.
        What's wrong?''
     A: You need to remove the limit on the stack size of processes.
        Under csh, try ``unlimit stack''.  This program uses an
        enormous (in the MB range) local array.  SUIF puts locals on
        the stack, so if you have low stack-size limits, which are
        often the default, the program will crash.

  3. Q: ``When I compile a program (on a non-MIPS machine, or on a
	MIPS machine with -s2c), why do I get errors like:

"/tmp/scc00684_5.out.c", line 227: syntax error at or near variable name "F"

        or other similar errors in a weird .out.c file?''
     A: The s2c backend, which is run by default on non-MIPS machines,
        or if you specify the -s2c option to scc, converts SUIF into C
        and then runs your native C compiler to generate an executable.
        The output of s2c is ANSI-C compliant, but many C compilers are
        unable to handle ANSI-C code.  You should use an ANSI-C compliant
        compiler, such as gcc, instead.  You can specify the name of
        another compiler with the "-cc name" option to scc, such as
        "-cc gcc".
