🚀 go-pugleaf

>God forbid, but there is probably some C program out there that relies
>on being able to:
>	int a,b, *ptr;
>
>	ptr = &a;
>	ptr++;
>	/* ptr now points to b */

No program that relies on that is correct C, so no compiler is
obliged to make them work.  In fact, the sooner such programs *are*
prevented, the better off we'll all be.

If the person *really* wanted that, they should have done

	int array[2], *ptr;

	ptr = &array[0];
	ptr++;
	/* ptr now points to array[1] */

and, if for some mysterious reason they insist on referring to these
objects as "a" and "b", they could do

	#define	a	array[0]
	#define	b	array[1]

Nowhere does C guarantee that contiguously-declared objects will be
given contiguous addresses in memory.