Ondřej Surý 063e05491b Disable C4090 MSVC warning ... MSVC documentation states: "This warning can be caused when a pointer to a const or volatile item is assigned to a pointer not declared as pointing to const or volatile." Unfortunately, this happens when we dynamically allocate and deallocate block of atomic variables using isc_mem_get and isc_mem_put. Couple of examples: lib\isc\hp.c(134): warning C4090: 'function': different 'volatile' qualifiers [C:\builds\isc-projects\bind9\lib\isc\win32\libisc.vcxproj] lib\isc\hp.c(144): warning C4090: 'function': different 'volatile' qualifiers [C:\builds\isc-projects\bind9\lib\isc\win32\libisc.vcxproj] lib\isc\stats.c(55): warning C4090: 'function': different 'volatile' qualifiers [C:\builds\isc-projects\bind9\lib\isc\win32\libisc.vcxproj] lib\isc\stats.c(87): warning C4090: 'function': different 'volatile' qualifiers [C:\builds\isc-projects\bind9\lib\isc\win32\libisc.vcxproj]		2020-04-15 12:47:42 +02:00
..
bind9	Set WarningLevel to Level1 for Release, treat warnings as errors	2020-04-15 12:45:05 +02:00
dns	Set WarningLevel to Level1 for Release, treat warnings as errors	2020-04-15 12:45:05 +02:00
irs	Set WarningLevel to Level1 for Release, treat warnings as errors	2020-04-15 12:45:05 +02:00
isc	Disable C4090 MSVC warning	2020-04-15 12:47:42 +02:00
isccc	Set WarningLevel to Level1 for Release, treat warnings as errors	2020-04-15 12:45:05 +02:00
isccfg	Set WarningLevel to Level1 for Release, treat warnings as errors	2020-04-15 12:45:05 +02:00
ns	Set WarningLevel to Level1 for Release, treat warnings as errors	2020-04-15 12:45:05 +02:00
samples	Set WarningLevel to Level1 for Release, treat warnings as errors	2020-04-15 12:45:05 +02:00
win32/bindevt	Set WarningLevel to Level1 for Release, treat warnings as errors	2020-04-15 12:45:05 +02:00
.gitignore	added gitignore, removed cvsignore	2012-03-03 23:10:05 -08:00
Kyuafile	link in lib/isccc/tests/Kyuafile	2018-11-13 07:23:36 +11:00
Makefile.in	remove lib/tests as nothing uses it anymore	2018-03-09 14:12:50 -08:00