outSecFileOff and the associated getFileOffset() accessors were
unnecessary.
For all the cases we care about, outSecFileOff is the same as
outSecOff. The only time they deviate is if there are zerofill
sections within a given segment. But since zerofill sections are always
at the end of a segment, the only sections where the two values deviate
are zerofill sections themselves. And we never actually query the
outSecFileOff of zerofill sections.
As for getFileOffset(), the only place it was being used was to
calculate the offset of the entry symbol. However, we can compute that
value by just taking the difference between the address of the entry
symbol and the address of the Mach-O header. In fact, this appears to be
what ld64 itself does. This difference is the same as the file offset as
long as there are no intervening zerofill sections, but since __text
is the first section in __TEXT, this never happens, so our previous
use of getFileOffset() was not wrong -- just inefficient.