> >On VMS, the compiler compiles and the linker links. :-)
>
> I suspect that's true on most systems. What might be different is that
> the command 'f90' (or 'ftn', or whatever it is called) is neither the
> compiler nor the linker but rather a driver or script that invokes the
> right executable(s) based on the options and files that follow.
Right.
> >Some unix
> >systems produce an executable by default and one has to add an option to
> >get just an object file.
> >
>
> I think that's the normal situation. Note that I said "compiles" and
> not "compilers" above.
You spotted my error! I did parse "compilers" instead of "compiles".
(Probably because I was expecting "compilations" in this case.)
> >However, producing an object file is overkill
> >if you want just syntax checking. At least with the VMS compiler, one
> >can specify /NOOBJECT (and specifying /NOOPTIMIZE makes sense here too)
> >to get essentially JUST syntax checking. With large codes and/or slow
> >(or heavily stressed due to other applications running) machines, this
> >can make things quite a bit faster.
>
> Right. That is what I think the original post was aiming for.
I agree.
> For the
> VMS compiler does /NOOPTIMIZE actually have any effect if you also
> specify /NOOBJECT?
I suspect that it doesn't, but I am not sure.
> For the Cray compiler the analog of /NOOBJECT is
> -dB (disable Binary creation). Not as descriptive, but in the Unix
> spirit. :)
Indeed!
|