Archiving ucode object files
Trevor Cotton
trevc at tecate.mips.com
Thu Apr 18 01:54:04 AEST 1991
In article <13160.2803307b at ecs.umass.edu>, gomatam at ecs.umass.edu writes:
|> I have the foll problem with archive ar:
|>
|> I have a bunch of files compiled under the foll:
|>
|> f77 -O3 *.f
|>
|> this is for a MIPS fortran compiler running on DEC 5000
|>
|> this produces a bunch of .u files (NOT the usual .o)
|>
|> supposedly, these are "ucode" optimized for speed, etc
|>
|> I need to link these files with other fortran source code; the problem is
|> creating a library of these files using ar
|>
|> I get an error "*.u is not in archive format"
|>
I don't know where this would be in the DEC documentation, but its documented
in the MIPS Language programmers guide chapter 4.
You should use the -j option to the compiler.
The resultant .u files can then be archived
e.g
cc -j one.c
cc -j two.c
cc -j three.c
ar crs libfoo.b one.u two.u three.u
Not that the convention for ucode libraries is libname.b
To load from a ucode library, use the -kl flag
e.g cc -O3 file1.u file2.u -klfoo -o outprog
Regards,
--
--trevc--
More information about the Comp.unix.questions
mailing list