:>
:>gcc tries to align stack to 16 byte boundaries as a speed
:>optiminzation. Why it doesn't do this in one instruction is beyond
:>me.
:
:Kocking 16 bytes off the stack pointer won't put it any closer to a
:16 byte boundary.
This is precisely my problem with gcc's 'optimization'. It's
utterly stupid for it to assume that the stack is already
16-byte aligned... it makes it impossible to mix aligned and
non-aligned code and still have a reasonably optimal result
(e.g. like third party libraries or older libraries or
whatever). And it's a huge, unnecessary waste of space
when most of the time all you are storing on the stack are
ints.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
