Age | Commit message (Collapse) | Author |
|
Makes it possible to build an i386 kernel with binutils-2.17 again.
ok miod@
|
|
|
|
xrstor, and xsaveopt.
based on kettenis's original that did xgetbv and xsetbv
ok kettenis@
|
|
Sendmail, Inc -> Proofpoint name change. See RELEASE_NOTES for
actual changes.
|
|
ok deraadt@
|
|
This includes additional functions to be protected --- those that
have local array definitions, or have references to local frame
addresses.
Miod verified that this works on real hardware, and not just on the
cross-compiled monster I tested this on.
|
|
One .Nm macro per name, and pass punctuation a as seperate argument.
Found with mandocdb(8).
OK jmc@.
|
|
which operates on element counts rather than buffer sizes. I'll start
annotating headers in a few weeks, after the hackathon. OK millert@.
|
|
additional functions to be protected --- those that have local array
definitions, or have references to local frame addresses.
Note 1: Han explicitly licensed this under GPLv2 for us.
Note 2: Do *not* use this anywhere in "src" Makefiles, as the other
GCC doesn't have this option yet (but I'm working on it).
|
|
size almost always has security implications. I think this quote
from Theo summarizes the situation best:
Which is why it is important to have at least one unforgiving
platform in the ecosystem which properly labels shit shit.
That's OpenBSD. If anyone can't handle that, they can go to platforms
which hide the reality.
|
|
ok miod@, matthew@
|
|
stpcpy, strcat, strcpy. Also don't simplify some safe builtins
into unsafe ones, otherwise we'll hit the linker with the bogus
warning. OK miod@, millert@.
|
|
work on alpha.
tested by naddy@, deraadt@
|
|
(long). Use (long long) and print it with %ll08x instead. ok zhuk@
|
|
|
|
sprintf, vsprintf, stpcpy, strcat, strcpy. We're hitting the linker
again, therefore the warning will show up now.
|
|
stderr separately so that redirections of gcc's stdout/stderr act as
expected.
ok and testing miod@
|
|
|
|
|
|
|
|
|
|
|
|
libcompat isn't needed; configure checks for the presence of cuserid()
and ftime() and the build copes well with the absence of either.
ftime() would only ever be used if gettimeofday() wasn't available,
and cuserid() is replaced by getlogin() but that code branch is not
reached anyway.
ok sthen@ jca@ deraadt@
|
|
discourage anyone from using anyways)
ok various
|
|
Kernel, base and ports seem happy with this change, and there's no
reason for collect2 to be less useful on these machines. Offending
lines in gcc/config found by Miod, thanks.
Let's commit the right file this time. ok kettenis@ miod@ mpi@
|
|
|
|
Kernel, base and ports seem happy with this change, and there's no
reason for collect2 to be less useful on these machines. Offending
lines in gcc/config found by Miod, thanks! ok kettenis@ miod@ mpi@
|
|
Makes sendmail happy on fs with large enough f_bavail values.
millert@ ok
|
|
Use useconds_t in the ualarm() declaration.
Bump libstdc++ major to be sure there isn't ABI issues.
ok deraadt@ jca@ jmc@ millert@
ports testing by landry@
|
|
found while working on mandoc apropos
|
|
debug information, gdb will either see calltrap or alltraps in the
stack trace of a kernel core file. To make the gdb backtrace command
work without debug information in the amd64 kernel, add the same
special case for alltraps as for calltrap.
OK miod@
|
|
OK deraadt@ miod@
|
|
on slower platforms. Idea from espie@, OK espie@ deraadt@ guenther@
|
|
as an ersatz for -W. Now that more and more third-party software assumes the
compiler supports -Wextra, this is definitely worth doing.
|
|
gcc 3 no longer defines this for us.
|
|
members to 64bit types. Assign new syscall numbers for (almost
all) the syscalls that involve the affected types, including anything
with time_t, timeval, itimerval, timespec, rusage, dirent, stat,
or kevent arguments. Add a d_off member to struct dirent and replace
getdirentries() with getdents(), thus immensely simplifying and
accelerating telldir/seekdir. Build perl with -DBIG_TIME.
Bump the major on every single base library: the compat bits included
here are only good enough to make the transition; the T32 compat
option will be burned as soon as we've reached the new world are
are happy with the snapshots for all architectures.
DANGER: ABI incompatibility. Updating to this kernel requires extra
work or you won't be able to login: install a snapshot instead.
Much assistance in fixing userland issues from deraadt@ and tedu@
and build assistance from todd@ and otto@
|
|
- provide 88110 syntactic sugar for the control register names
- correctly handle -m options
- and a minor fix to allow the register prefix to correctly be recognized in
front of the condition codes (only needed for SVR4)
|
|
applied for all archs.
ok deraadt@ miod@
|
|
simplification and ok kettenis@
|
|
httpd correction and ok kettenis@
|
|
|
|
matches the behaviour of gcc >= 4.3 and clang
ok miod@
|
|
considerations.
|
|
it had required some generous bandaid), but unfortunately not able to compile
most of the Real World (tm) software.
|
|
Change the logic depending upon COMPILER_VERSION everywhere, to assume gcc4
is the norm and to explicitely test for gcc3 when a different behaviour
is required.
No functional change intended. Be sure to `make install' in share/mk before
attempting to do anything.
|
|
|
|
with an optimization pass which attemps to identify and remove dead stores.
Unfortunately, this logic assumes that a given rtl MEM reference can only
refer to register contents and values, but not further dereference memory.
This is not true of all addressing modes on vax, and this causes gcc 3 to
consider as dead stores everything which can be expressed as *offset(register)
in vax assembly. The canonical example of this is linked list insertion or
removal, with instructions such as "item->prev->next = item->next" being
wrongly optimized out, and cause double frees or other funny linking problems
later on.
Add a knob to disable the troublesome part of that optimization pass, and
only enable this knob on vax.
This gives a native vax gcc 3 compiler able to rebuild the world.
|
|
considerations.
|
|
considerations.
|
|
|