| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
get rid of bsd.kern.mk completely.
OK'ed by: bde
|
|
|
|
|
|
|
|
|
| |
Always use sys/conf/kern.mk when building kernel/modules.
<bsd.kern.mk> is only preserved for sys/boot/pc98/boot2
for now, but this will be fixed. If there are other
users of <bsd.kern.mk>, please let me know.
Reminded by: bde
|
|
|
|
|
| |
- Moved special compiler flags to bsd.kern.mk so they get used for modules
too.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix the "@gprel relocation against dynamic symbol xxx" linker error.
Variables defined in the link unit and small enough to be put in the
short data section will have a gp-relative access sequence (using the
@gprel relocation). It is invalid to have @gprel relocations in shared
libraries, because they are to be resolved by the static linker and
not the dynamic linker. The -fpic option will cause @ltoff relocations
for @gprel relocations, but the side-effects are untested (if any).
Instead, disable/eliminate the short data section to achieve the same.
|
|
|
|
|
|
| |
This reduces the size of GENERIC's text space by 73999 bytes (about 2%).
The bloat is from approximately 3437 strings longer than 31 characters
being padded to a 32-byte boundary.
|
|
|
|
|
|
|
| |
ev6 or pca56 etc this downgrades the cpu specification passed to gas.
As a result, gas will fail when gcc generates media instructions (in
uipc_usrreq.c). This only affects what gas will accept, not what gcc
generates or what our *.s file contain.
|
|
|
|
|
|
| |
the gcc lossage that caused it to be turned off was fixed.
Tested with: i386/{GENERIC,LINT,...}, alpha/GENERIC
|
|
|
|
|
|
| |
back to -fformat-extensions (or whatever) when we have the functionality.
We are gaining warnings again that should be fixed but the are being hidden
by NO_WERROR and all the -Wformat noise.
|
| |
|
|
|
|
|
| |
in a kernel config file. This should minimize the tearing-out-hair process
while updating the kernel for gcc-3 compliance.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
I should have done it that way in the first place.
Pointed-out-by: bde
|
|
|
|
| |
Submitted by: Allen Campbell <allenc@verinet.com>
|
|
|
|
| |
This reduces the size of the kernel and modules when compiled with GCC 2.95.
|
| |
|
|
|
|
|
|
| |
is not implied by -Wall as claimed by gcc.1. Adding it causes a
measly 7193 new warnings for LINT, mostly for "unused parameter" and
"comparison between signed and unsigned".
|
| |
|
| |
|
|
|
|
|
|
| |
kernel modules are built with the right flags.
Suggested by: Andrew Gallatin <gallatin@cs.duke.edu>
|
|
|
|
| |
Reviewed by: cvs-committers@freebsd.org
|
|
|
|
|
| |
-current version of gcc. Without it, -Wformat would complain about all
the nonstandard %[Dbrz] formats in the kernel.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
variables were lost when we removed -W, and 23 new ones including at
least one serious one have crept in for LINT.
Restored -Winline to CFLAGS. This gives only 3 old warnings and 1 new
for LINT.
|
| |
|
|
|
|
|
|
|
|
| |
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
|
|
|
|
|
|
|
|
|
|
|
|
| |
2.2 are more obvious. -Winline is unimportant, but -W gives thousands
of warnings for comparisions. Turning off -W also loses warnings for:
- auto variables clobbered by longjmp. Not much of a problem in the kernel.
- functions returning without a value. I don't like losing this.
- an expression statement or the left side of a comma operand contains no
side effects. Turning this off also stops warnings for the low quality
debugging macros in gsc.c and lpt.c.
Should be in 2.2.
|
|
|
|
|
|
|
| |
Also disabled -Wunused. It caused too many warnings even for me.
The sign mismatch warnings should be fixed first. They are more
important and harder to disable (they are controlled by -W, which
controls too many things).
|
|
Centralized the definition of CWARNFLAGS into bsd.kern.mk.
|