Stable CVS 1.11.15 has been released. Stable releases contain only
bug fixes from previous versions of CVS. This version fixes serious
security holes in both the client and the CVS server executables
as well as fixing many other bugs, including some file resurrection
issues. We recommend this upgrade for all CVS clients and servers!
2003-07-10 Kazu Hirata <kazu@cs.umass.edu>
PR c/11449
* fold-const.c (sign_bit_p): Return EXP if VAL is the sign bit
of HOST_WIDE_INT.
(fold_single_bit_test): If sign_bit_p() fails, assume that the
bit being tested is not a sign bit.
2003-07-04 Jeff Law <law@redhat.com>
PR c/11428
* expr.c (do_store_flag): Pass in the correct result type
when calling fold_single_bit_test.
* fold-const.c (fold_single_bit_test): Use result_type for the
result when folding a sign bit test.
2003-07-02 Jeff Law <law@redhat.com>
* expr.c (do_store_flag): Remove special case folding for
single bit tests. Instead call back into the commonized folder
routine.
* fold-const.c (fold_single_bit_test): New function, mostly
extracted from do_store_flag, with an additional case extracted
from fold.
(fold): Call fold_single_bit_test appropriately.
* tree.h (fold_single_bit_test): Prototype.
configuration to enable inbound mail reception.
This is in line with general security policy, so that postfix is
"safe" until other required configuration steps have been taken.
This way, systems enabling this mailer for local mail delivery only
won't be vulnerable to surprise exploits, being used as relays,
/var/mail filling up with spam, etc.
http://www.ffii.org/cgi-bin/viewcvs.cgi/groff/Makefile.comm
(The previous fixes still ended up with syntactically-invalid shell
code for the 'for' loops, which would fail on some versions of linux.
The ignore-error marking for the command would allow the build to finish,
but it would leave extraneous "Failed" bits in the build output.)
2003-06-22 Jason Thorpe <thorpej@wasabisystems.com>
* config/tc-ns32k.c (md_begin): Initialize inst_hash_table after
all locals have been declared.
from the binutils mainline.
Problem (and also fix) reported by Eyal Lebedinsky on port-pc532.
Fix the behaviour of native and tools gcc when MKPIC=no is specified for
platforms that mknative has determined support shared libraries.
XXX distrib/sets/sets.subr doesn't support MKPIC=no
The condition of the check if we are at a safe point to pause (i.e. we're not
holding a lock) was inverted. Suspending the client did result in the
server using upto datalimit memory, because the server child process did
continue producing output while the server parent was holding back output
to the client.
and exception handling have a chance of working properly.
- creates libgcc, libgcc_eh and libgcc_s
- updates LIBGCC_SPEC to use them appropriately.
There's a hack in here at the moment with respect to libgcc_so in that it
is preferable to link against libgcc_so will only when -shared-libgcc is
specified (the c++ frontend does this automatically.) Configurations where
LINK_EH_SPEC is defined already do this. The gcc configuration for
NetBSD/alpha and another NetBSD platform (I forget which) actually define
LINK_EH_SPEC probably by accident rather than design.
- updates share/mk to use the compiler's knowledge of what needs linking into
libraries and executables. This removes an hppa hack.
- updates the sets for the newly created libgcc* files.
- support for linking against the _pg version of libgcc has been removed.
- Disable symbol versioning (for now)
- Make sure that libiberty knows its being configured with a
cross compiler.
- The CXX_* variables are no longer needed/used.
- LIB2FUNCS_EXTRA gets pulled in via LIB2ADD
- Get LIB1ASMFUNCS and LIB2ASMSRC
- MAYBE_USE_COLLECT2 got renamed to USE_COLLECT2 (but might not
be used)
- Get EXTRA_HEADERS so that we get generate the right paths for
CPPFLAGS
- Get some variables related to shared libgcc
default broken flags. groff 1.19 defaulted to this value off, whereas
groff 1.18.1 and earlier defaulted to this being on. Setting this value
fixes postscript printing to my HP LJ4m.
Note: BROKEN_SPOOLER_FLAGS was previously `7', so we were already enabling
workarounds for other issues...
from GENTOO LINUX SECURITY ANNOUNCEMENT 200312-08
"Stable CVS 1.11.11 has been released. Stable releases contain only
bug fixes from previous versions of CVS. This release adds code to
the CVS server to prevent it from continuing as root after a user
login, as an extra failsafe against a compromise of the
CVSROOT/passwd file. Previously, any user with the ability to write
the CVSROOT/passwd file could execute arbitrary code as the root
user on systems with CVS pserver access enabled. We recommend this
upgrade for all CVS servers!"
date: 2003/07/09 01:27:30; author: cgd; state: Exp; lines: +3 -2
2003-07-08 Chris Demetriou <cgd@broadcom.com>
* config/tc-mips.c (mips_validate_fix): Do not warn about branch
target being a global symbol if not compiling SVR4 PIC code.
Fixes warnings compiling MIPS kernels. Problem noticed by Izumi Tsutsui
on the port-pmax list.
PR optimization/13037
* loop.c (update_giv_derive): Ignore redundant sets of a biv
when calculating how to derive a giv from a biv.
This fixes the underlying problem in toolchain/23002.
and without Kerberos 4 & 5 (MKKERBEROS=no). Previously checkflist
complained of missing files.
* move kerberos- and kerberos 4-only files into new flists,
distrib/sets/lists/*/krb.*
* make the flist generators grok MKKERBEROS{,4} variables
* fix Makefiles which treat MKKERBEROS=no as MKKERBEROS5=no.
9 out of 10 experts agree that it is ludicrous to build w/
KERBEROS4 and w/o KERBEROS5.
* fix header files, also, which treat MKKERBEROS=no as MKKERBEROS5=no.
* omit some Kerberos-only subdirectories from the build as
MKKERBEROS{,4} indicate
(I acknowledge the sentiment that flists are the wrong way to go,
and that the makefiles should produce the metalog directly. That
sounds to me like the right way to go, but I am not prepared to do
revamp all the makefiles. While my approach is expedient, it fits
painlessly within the current build architecture until we are
delivered from flist purgatory, and it does not postpone our
delivery. Fair enough?)
on these platforms so far:
- alpha, arm, i386, mipseb, mipsel, sparc64
built but not yet tested on:
- armeb, sparc, amd64
build errors (mostly not related) on:
- hppa, m68000, m68k, macppc, sh3el, sh3eb, vax
XXX again this is not everything required; many other changes in
XXX already used files are left out.
is moving here, keeping everything together.
tested with: vax (old config), mac68k (old config), i386 (new config)
and shark (new config). tested i386 binaries only so far, but the
system seems to be surviving the self-hosted test.
XXX: note that this isn't *all* the bits required to run a binutils
2.14 world for arm or i386; these will come soon enough...
