>>>>> "Roman" == Roman Kennke <[EMAIL PROTECTED]> writes:
Roman> Then we can use shorter macro names or even better function Roman> calls like cp_mem_alloc() or something similar. Can we use the standard names, and then require the more bizarre ports to do things like "#define malloc BlahBlah"? The issue that came up here yesterday on irc is that, apparently, some of these macros are only needed for ports that won't be in Classpath. Roman> - memcpy (_dst + dst_offset, src, dst_len); Roman> + TARGET_NATIVE_MEMORY_FAST_COPY(src + index,_dst + dst_offset,dst_len); There are still platforms without memcpy? What are they? This seems like a great place for a target port to provide a replacement function or macro. Tom _______________________________________________ Classpath-patches mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath-patches
