malloc impossible?

[Doug Gwyn]

In article <1010 at vsi.COM> friedl at vsi.COM (Stephen J. Friedl) writes:
>> One can imagine a machine with different spaces for each different
>> intrinstic data type, where malloc() has to select from one of 8
>> or 16 possibilities.  Of course, since malloc() gets only one argument,
>> it has no way to decide which address space to use.
>Wow. Wouldn't structs be *really* interesting on a machine like this?

Don't worry, unless all those spaces are "shadowed", C cannot be
implemented on it.

X3J11 was very careful to ensure that memcpy() could be implemented
portably in ANSI C in the obvious way.

The talk about different kinds of data spaces is thus a red herring.