George Koehler e97116c037 Remove some obsolete code that causes a gcc warning. ... In my OpenBSD/amd64 system, the code becomes if (0) outname.on_valu &= ~(((0xFFFFFFFF)<<32)<<32); The 0xFFFFFFFF is a 32-bit int, so the left shift by 32 is out of range and causes the gcc warning. The intent might be to clear any sign-extended bits, if the assignment outname.on_valu = valu did sign extension. Old C had no unsigned long, so .on_valu would have been long. The code is obsolete because h/out.h now declares .on_valu as uint32_t.		2017-01-16 18:09:55 -05:00
..
as	Remove some obsolete code that causes a gcc warning.	2017-01-16 18:09:55 -05:00
cg	Distributions are a pain --- let's not bother any more. Instead, we just tag	2016-09-02 23:00:38 +02:00
fp	Distributions are a pain --- let's not bother any more. Instead, we just tag	2016-09-02 23:00:38 +02:00
grind	Distributions are a pain --- let's not bother any more. Instead, we just tag	2016-09-02 23:00:38 +02:00
libg	Distributions are a pain --- let's not bother any more. Instead, we just tag	2016-09-02 23:00:38 +02:00
mcg	Add a test (currently failing) to check that Pascal char sets can store all 256	2017-01-15 22:28:14 +01:00
ncg	Ensure that memory is zero-initialised.	2017-01-16 22:45:03 +01:00
top	Fix buffer overrun: if LABEL_STARTER is seen but LABEL_TERMINATOR is not, the	2016-11-13 14:04:58 +01:00