[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cp-patches] FYI: java-nio adjustments for target/native
From: |
Tom Tromey |
Subject: |
Re: [cp-patches] FYI: java-nio adjustments for target/native |
Date: |
18 Jan 2006 14:29:42 -0700 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 |
>>>>> "Roman" == Roman Kennke <address@hidden> 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