| Age | Commit message (Collapse) | Author |
|---|
|
functions which are too greedy in stack variables.
This is intended to be used for kernel compiles, where this warning will
be enabled for a reasonable size (after a few weeks grace period so that
people can upgrade their compiler).
Please note that this warning relies upon md code, and as such is only
available on platforms OpenBSD runs on; also, the stack size being warned
on is only the local variables size, regardless of the ABI stack usage
requirements and the callee-saved registers; which means a function may
be warning-clean yet need more stack space than meets the eye; the
actual size being checked on may change to include these extras in the
future.
|
|
generation issues.
|
|
Approved deraadt@, kettenis@
|
|
with cpp -traditional, but it should be enough for lint.
okay miod@
|
|
who is too shy to commit it.
|
|
|
|
defined in terms of long, not int on all architectures.
|
|
Based on existing bits for FreeBSD 5
|
|
miod@ checked this does not impact builds on old arches.
|
|
from miod@
|
|
gcc 2.95.
tests and okay miod@, marc@.
|
|
921215-1 gcc testsuite.
|
|
ok espie@
|
|
ok kettenis@
|
|
This makes a noticeable performance improvement on 68060, especially for
crypto operations (such as ssh), with basically no loss on 680[234]0.
ok deraadt@
|
|
to build a gcc3 sparc.
(reviewed and accepted upstream)
|
|
|
|
the machine architecture. We now output amd64 instead
of x86_64 as it should be.
ok deraadt@ pvalchev@
|
|
to find each other.
okay niklas@ (`deja-vu')
|
|
"doh! ok!" niklas@ ;-)
|
|
Spotted by espie@
|
|
|
|
|
|
inter-library function calls where the callee would change the GOT register
but not restore it when returning to its caller.
Helps immensely libpthread, as well as dynamically-linked X11 clients.
Fromm gcc 3; tested by matthieu@, nick@ and todd@; ok deraadt@
|
|
|
|
when doing bounds checking (bug revealed by mmap malloc).
Noticed by krause@, tested otto@
|
|
changes address incorrect stack usage, when optimization needs more
nameless temporary values than available registers, and has to save them
on stack.
In some (rare) circumstances, it will compute a stack address _outside_
the current function local storage space, overwriting the caller's stack.
Most of the time, this only affects the "outgoing argument area", which is
harmless if it has not been populated; this explains why it has not been
noticed earlier.
Since I see no easy way to fix this, I decided to go the simpler way of
removing this ougoing argument area. This not only reduces stack usage,
but also makes varargs/stdarg code smaller and faster; also functions which
get their first few arguments in registers, then some on the stack, then
some in registers again, will not allocate stack space for the second
set of arguments passed through registers.
This is an ABI change, we are no longer 88Open compliant (have we ever
been?).
|
|
work for code compiled at -O0...
|
|
knowing that the area we are using is correctly aligned.
Produces smaller and faster code (about 0.8% time decrease in a complete
build, which amounts to roughly 15 minutes).
|
|
for registers if at least one nameless argument is passed through registers;
instead, only allocate as many bytes as necessary.
Slightly reduces stack usage; no ABI change.
|
|
current_function_{stdarg,varargs} instead of homegrown implementation, etc.
No functional change.
|
|
fixes C++ exceptions.
this relies on an earlier libstdc++ bump
|
|
and they have different major numbers to prevent collision.
|
|
To build you must:
cd /usr/src && make obj && make includes
cd lib/libc && make depend && make && NOMAN=1 sudo make install
cd /usr/src && make build
|
|
The problem really only arises when optimize_reg_copy_3() attempts to
merge a load which fits in a register and a load which does not fit - in
the m68k case, merging an int32_t foo and (int64_t)foo two lines later.
In this case, and only if the backend provides its own expansion of the
extendsidi2 insn (usually for performance and code size reasons) as
embedded assembly statements but not rtl operations, then gcc at this
point will ``fail to realize'' that when sign-extending (or
zero-extending) the value of rN into rN and r(N+1), the value of rN is
not preserved on big-endian architectures, and the optimization will
produce bad code.
Of all the OpenBSD-supported platforms, arm and m68k are the only
affected; but further optimizations in gcc3 (on arm) apparently neuter
this bug, which I have been unable to reproduce in an arm build with
gcc3.
This commit works around the problem by preventing expansions larger
than the width of a general register, on m68k only. Other platforms are
not affected.
|
|
|
|
This is a workaround for lines 1055-1057 of tcp_input.c being miscompiled,
though the problem looks like missing use/clobber qualifiers in the
extendplussidi insn, rather than a specific optimize_reg_copy_3() issue.
A proper fix may be devised in the future, in the meantime this allows
m68k platforms to be back in track.
|
|
No functional change, it's just faster.
|
|
and the reload phase when compiling complex code, and the fix is non-trivial.
|
|
|
|
and FUNCTION_ARG_ADVANCE fixes in m88k.c, allow the optimized bcopy
sequences to be reliable again, so enable them back.
|
|
parameter is going to hit the stack.
|
|
__builtin_saveregs(); no functional change.
|
|
ok deraadt@
|
|
pass all the subsequent arguments on the stack.
This is necessary for proper varargs operation, if used.
|
|
|
|
|
|
|
|
* caller-save.c (mark_referenced_regs): Mark partially-overwritten
multi-word registers.
This problem apparently only affected m88k, as far as OpenBSD is concerned.
|
|
ok deraadt@, millert@, krw@ - mdoc ok jmc@
|
