Home | History | Annotate | Download | only in ssp
History log of /src/tests/lib/libc/ssp/Makefile
RevisionDateAuthorComments
 1.12  10-Nov-2023  christos PR/57689: RVP: getcwd() not overridable with -D_FORTIFY_SOURCE
 1.11  03-Jun-2023  lukem bsd.own.mk: rename GCC_NO_* to CC_WNO_*

Rename compiler-warning-disable variables from
GCC_NO_warning
to
CC_WNO_warning
where warning is the full warning name as used by the compiler.

GCC_NO_IMPLICIT_FALLTHRU is CC_WNO_IMPLICIT_FALLTHROUGH

Using the convention CC_compilerflag, where compilerflag
is based on the full compiler flag name.
 1.10  13-Oct-2019  mrg introduce some common variables for use in GCC warning disables:

GCC_NO_FORMAT_TRUNCATION -Wno-format-truncation (GCC 7/8)
GCC_NO_STRINGOP_TRUNCATION -Wno-stringop-truncation (GCC 8)
GCC_NO_STRINGOP_OVERFLOW -Wno-stringop-overflow (GCC 8)
GCC_NO_CAST_FUNCTION_TYPE -Wno-cast-function-type (GCC 8)

use these to turn off warnings for most GCC-8 complaints. many
of these are false positives, most of the real bugs are already
commited, or are yet to come.


we plan to introduce versions of (some?) of these that use the
"-Wno-error=" form, which still displays the warnings but does
not make it an error, and all of the above will be re-considered
as either being "fix me" (warning still displayed) or "warning
is wrong."
 1.9  29-Sep-2019  mrg convert HAVE_GCC == 7 to HAVE_GCC >= 7.
 1.8  04-Feb-2019  mrg - tests explicitly check failure modes, ignore those warnings
 1.7  06-Apr-2014  christos branches: 1.7.24;
add stp*cpy() tests
 1.6  23-Sep-2012  joerg branches: 1.6.6;
Update LLVM/Clang snapshot to r164464. This adopts the GCC options for
the SSP parameters and a not-yet-default rewrite of SROA.
 1.5  04-Apr-2012  joerg branches: 1.5.2;
Disable new -Wstring-plus-int warning where needed for now.
Adjust various places that add GCC-only options to check for the active
compiler first.
 1.4  12-Jun-2011  plunky branches: 1.4.2;
reinstate ssp:raw test, slightly differently.. this one is built
with -fstack-protector-all and tests that the compiler built in
stack protection works, by poking directly outside the buffer
 1.3  12-Jun-2011  plunky don't pass -fstack-protector for these, the tests are actually for the
__*_chk functions included by -D_FORTIFY_SOURCE=2, and if the compiler
provides additional protection, it can mask broken functions..

(none of the _chk functions will return or process any data if
the length given is known to be larger than the buffer)
 1.2  26-Feb-2011  pgoyette branches: 1.2.2;
The ssp/raw test is useless. Remove it.
 1.1  27-Dec-2010  pgoyette branches: 1.1.2;
Migrate the ssp tests from regress to atf.

Of the 17 tests, 4 fail in both the regress and atf style. 3 additional
tests fails in atf that did NOT fail in regress: gets, fgets, and read.
I will investigate why, and update when I can, but it is still useful to
get these tests into the new format where they can be exercised.
 1.1.2.1  05-Mar-2011  bouyer Sync with HEAD
 1.2.2.1  23-Jun-2011  cherry Catchup with rmind-uvmplock merge.
 1.4.2.3  22-May-2014  yamt sync with head.

for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.

this commit was splitted into small chunks to avoid
a limitation of cvs. ("Protocol error: too many arguments")
 1.4.2.2  30-Oct-2012  yamt sync with head
 1.4.2.1  17-Apr-2012  yamt sync with head
 1.5.2.2  20-Aug-2014  tls Rebase to HEAD as of a few days ago.
 1.5.2.1  20-Nov-2012  tls Resync to 2012-11-19 00:00:00 UTC
 1.6.6.1  10-Aug-2014  tls Rebase.
 1.7.24.2  13-Apr-2020  martin Mostly merge changes from HEAD upto 20200411
 1.7.24.1  10-Jun-2019  christos Sync with HEAD

RSS XML Feed