search for: wd4018

...ed that driver developers should not choose to ignore, and this is one of them... /wd4242 (which is how you disable warnings in WDK), is one of the things I tried before going /W2, only to find that, unlike other warnings, which I double-checked you can actually silence with /wd (for instance /wd4018 --signed/unsigned mismatch-- can be disabled alright), this one could not be silenced. Regards, /Pete

Hi Shao, You're right, "a=b=<immediate value>;" wasn't the actual issue. On 2016.03.06 20:34, Shao Miller via Syslinux wrote: > If this change is simply due to a mental note about an incident where a > compiler once complained about this type of thing The problem was due to the following warning when compiling for 64-bit using using the latest WDK (7600.16385.1),