projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| ad4f09a5 KT |
1 | .pa 1 |
| 2 | .he 'RELOC (I)'2/7/73'RELOC (I)' | |
| 3 | .ti 0 | |
| 4 | NAME reloc -- relocate object files | |
| 5 | .sp | |
| 6 | .ti 0 | |
| 7 | SYNOPSIS reloc\b\b\b\b\b_____ file [-\b_]octal [ -\b_ ] | |
| 8 | .sp | |
| 9 | .ti 0 | |
| 10 | DESCRIPTION reloc\b\b\b\b\b_____ | |
| 11 | modifies the named object program file so that it will operate correctly | |
| 12 | at a different core origin than the one for which | |
| 13 | it was assembled or loaded. | |
| 14 | ||
| 15 | The new core origin is the old origin | |
| 16 | increased by | |
| 17 | the given octal\b\b\b\b\b_____ | |
| 18 | number (or decreased if the number has a "-" sign). | |
| 19 | ||
| 20 | If the object file was generated by the link-editor ld\b\b__, | |
| 21 | the "-r" ld\b\b__ option must have been given to | |
| 22 | preserve the relocation information in the file. | |
| 23 | ||
| 24 | If the optional last argument is given, then any | |
| 25 | "setd" instruction at the start of the file | |
| 26 | will be replaced by a no-op. | |
| 27 | ||
| 28 | The purpose of this command is to simplify the | |
| 29 | preparation of object programs for systems | |
| 30 | which have no relocation hardware. | |
| 31 | It is hard to imagine a situation | |
| 32 | in which it would be useful to attempt directly to execute | |
| 33 | a program treated by reloc\b\b\b\b\b_____. | |
| 34 | .sp | |
| 35 | .ti 0 | |
| 36 | FILES -- | |
| 37 | .sp | |
| 38 | .ti 0 | |
| 39 | SEE ALSO as(I), ld(I), a.out(V) | |
| 40 | .sp | |
| 41 | .ti 0 | |
| 42 | DIAGNOSTICS As appropriate | |
| 43 | .sp | |
| 44 | .ti 0 | |
| 45 | BUGS -- |