code alignment - mod 16 vs mod 4

code alignment - mod 16 vs mod 4

Post by Phil Jens » Sat, 21 Jan 1995 01:43:56



As this may affect kernel efficiency, I thought I'd ask:  in my (Slackware)
1.0.9 kernel, the compiler obviously used an alignment of 16, but the loader
used 4.  So as you read through zSystem.map, for a while all the entry points
end in 4, then c, then 0...  If 16-byte alignment is worth doing, it's worth
doing right - this way just wastes space.  So I ask - is this still happening?

Another compilation thing - has anyone ever actually benchmarked kernel speed
with and without -fomit-frame-pointer?  I haven't, but I've looked at SIZE,
which is about 3% LARGER with -fomit...  Why?  Every frame reference is one
byte longer (the "s-i-b" byte - necessary to get references off of %esp).

Phil Jensen, happy full-screen-TECO user