| Age | Commit message (Collapse) | Author |
|---|
|
calculate_can_reach_end skips the NOTE_INSN_FUNCTION_END with _ssp_ label to the original NOTE_INSN_FUNCTION_END.
ok otto
|
|
|
|
link libc.
|
|
|
|
|
|
ok markus@ drahn@
|
|
ok deraadt@
|
|
|
|
Disable building of cxxfilt in gcc, build it from its own directory.
|
|
instruments for every functions.
ok pvalchev@
|
|
functions.
ok pvalchev@
|
|
ok pvalchev@
|
|
the contents of DECL_RTL (parms).
ok pvalchev@
|
|
of your beliefs are wrong.
In this case, trust in gcc.
When computing the address of a field in a structure on stack, and:
- the offset of the structure relative to the stack pointer
and
- the offset of the field relative to the structure
have no _bits_ in common (for example, accessing field at structure(8)
with the structure at sp(64)), triggers a gcc optimization in the following
improvement:
(plus (plus (frame_pointer offset_for_structure) offset_for_field))
changing into
(plus (frame_pointer direct_offset_for_field))
In the aforementioned "no bits in common" case, gcc will use
(or (plus frame_pointer offset_for_structure) offset_for_field)
which is not necessarily correct, depending on the value of the frame
pointer...
Checking generated assembly code for a kernel compilation pointed out that
ALL architectures were affected by this bug (some, such as m88k, alpha
and sparc64, being much more affected than others, such as vax and m68k).
Our first move was to backport a fix for this found in the gcc 3.x branch,
however it relies upon several microbugfixes scattered around, and produced
a misbehaving kernel on one particular machine. So what goes in with this
commit is just a conservative fix which disables this particular "bitwise or
is fun" optimization.
Problem discovery and analysis by yours truly. Fix by etoh@ and I.
Tested on all supported architectures by various people, including deraadt@,
henning@, mickey@, naddy@ and I.
|
|
This switch forces block copy operations to always fallback to memcpy()
when it is not done by inline load and stores, rather than using the
m88k movstr* functions found in libgcc.
The name of this option has been choosen after the mips back end, which
has a similar option.
Right now, this is a no-op since these functions are disabled due to (yet)
another gcc bug; but this will help building standalone code, such as the
kernel and boot blocks, without having to link against libgcc.
|
|
on negative values. Suppresses some warnings on code which is useless
but legal. deraadt@ ok
|
|
- use .Sq
|
|
- section reorder
- use .Sq instead of `'
- kill whitespace
- typos
|
|
improves diffability against stock gcc sources, for us alzheimer-impaired
people. Requested by deraadt@
(no functional change)
|
|
every object by default. ok avsm@ henning@ marc@
|
|
http://gcc.gnu.org/ml/gcc-bugs/1999-08n/msg00621.html
and described in the related thread.
This particular problem used to not be triggered (or not often), but the
use of propolice affects the instruction flow, and started triggering it
more often, for example in Qt's qmenubar class.
Ironically, running with /etc/malloc.conf->AJ would neuter the bug in this
case...
Problem tracked by espie@ and etoh@, tested by various, ok deraadt@
|
|
This changes the real definition to __mcount, but with a weak mcount
for compat. On the next major bump the weak alias should be removed.
Without this diff the compiler symbol mcount conflicts with the
user mcount() function.
|
|
|
|
|
|
for example when -fexpensive-optimizations is used, sometimes causes incorrect
code sequences to be generated.
As -fexpensive-optimizations is implied by -O2, this means we are potentially
affected by this in numerous places... so add a specific workaround to nullify
expensizve-optimizations in preserve_subexpressions_p() on a
known-to-be-affected basis.
So far, only alpha, powerpc, m88k, sparc and sparc64 are affected.
Problem tracked down by henning@ - analysis by etoh@ and I - ugly workaround
by me - ok deraadt@
|
|
hundred bytes) block copies. While the functions themselves are probably
optimal or not far from it, the code responsible for their invocation is not,
and has a bad tendency of miscomputing the destination buffer address,
especially when optimization is used.
This is a temporary measure, these functions will be reenabled once a good fix
is ready.
ok deraadt@ espie@
|
|
of erroring out in a later sanity check. Error noticed by jolan@
This only affects the -Wbounded case
|
|
Configuration settings mostly borrowed from the former gcc 2.8 configuration.
A few typos and fixes backported from gcc 3.3, and a hell lot of fixes from
my fingertips.
This is enough to yield a compiler which will produce correct code at -O0.
Optimization is slightly broken for some constructs, and more fixes are in
the pipeline.
ok deraadt@
|
|
(vfp const))". The incoming_args alone is derived from the address operation of the 1st function argument. This fixes to protect the 1st function argument from buffer overflow.
ok pvalcehv@
|
|
at modifying the argument information.
ok pvalchev@
|
|
The incoming_args alone is derived from the address operation of the 1st function argument. This fixes to protect the 1st function argument from buffer overflow.
ok pvalchev@
|
|
|
|
format args (%r,%z,%:,%b). A step towards reenabling -Wformat in the
kernel again ...
deraadt@ ok
|
|
|
|
the libc functions are in place, remove HARD_QUAD from sparc64. (If you
actually want it, for some demented reason, look at -mhard-quad-float,
void where prohibited).
|
|
convention for the _Qp_* functions. Rather than fix it, rely on the
fact that it does produce correct calls to the _Q_* functions and
provide a shim in libc (already committed) to deal with it.
|
|
ok drahn@
|
|
deraadt@ ok
|
|
with mdoc help from jmc@, deraadt@ ok
|
|
length passed to common functions such as strlcpy/strlcat match the
real length of the buffer. It also checks to make sure that the bound
length was not incorrectly derived from a sizeof(pointer) operation.
Functions must be marked with the new attribute __bounded__, and warnings
are turned on by -Wbounded. Specifying -Wformat also enables bounds
checking for scanf(3) bounds to '%s' format variables. -Wall now turns
on -Wbounded also.
The checking is pretty limited right now to constant parameters, and the
buffers must be statically declared, and not inside a record type. This
simple checking still found hundreds of bugs around the ports tree though,
and there have been no false positive warnings.
10x to niklas@, Richard Sharp and David Scott {rich,dave}@recoil.org for
compiler advice. deraadt@ ok, miod@ tested on his collection of hardware
You need to recompile gcc now if source upgrading in -current before
doing a make world.
|
|
skip the canonicalization; (minus A (plus B C)) to (minus (minus A B) C) where B is frame pointer and C is frame offset.
ok pvalchev@
|
|
following RTL conversion; (plus (plus fp offset) const) to (plus (plus fp const) offset).
ok pvalchev@
|
|
|
|
|
|
pvalchev@ fgsch@ millert@ ok
|
|
|
|
|
|
|
|
okay tdeval, fries, tdeval, millert...
|
|
rescinded 22 July 1999. Proofed by myself and Theo.
|
