代码搜索：Overlapping
找到约 346 项符合「Overlapping」的源代码
代码结果 346
www.eeworm.com/read/162519/5540898
c cls_6_1_byte.c
/* Area: ffi_call, closure_call
Purpose: Check structure passing with different structure size.
Depending on the ABI. Check overlapping.
Limitations: none.
PR: none.
Originator:
www.eeworm.com/read/162519/5540904
c cls_7_1_byte.c
/* Area: ffi_call, closure_call
Purpose: Check structure passing with different structure size.
Depending on the ABI. Check overlapping.
Limitations: none.
PR: none.
Originator:
www.eeworm.com/read/162519/5540909
c cls_16byte.c
/* Area: ffi_call, closure_call
Purpose: Check structure passing with different structure size.
Depending on the ABI. Check overlapping.
Limitations: none.
PR: none.
Originator:
www.eeworm.com/read/162519/5540921
c cls_4byte.c
/* Area: ffi_call, closure_call
Purpose: Check structure passing with different structure size.
Depending on the ABI. Check overlapping.
Limitations: none.
PR: none.
Originator:
www.eeworm.com/read/162519/5540922
c cls_5byte.c
/* Area: ffi_call, closure_call
Purpose: Check structure passing with different structure size.
Depending on the ABI. Check overlapping.
Limitations: none.
PR: none.
Originator:
www.eeworm.com/read/162519/5540938
c cls_7byte.c
/* Area: ffi_call, closure_call
Purpose: Check structure passing with different structure size.
Depending on the ABI. Check overlapping.
Limitations: none.
PR: none.
Originator:
www.eeworm.com/read/162519/5540941
c cls_20byte.c
/* Area: ffi_call, closure_call
Purpose: Check structure passing with different structure size.
Depending on the ABI. Check overlapping.
Limitations: none.
PR: none.
Originator:
www.eeworm.com/read/162519/5540951
c cls_20byte1.c
/* Area: ffi_call, closure_call
Purpose: Check structure passing with different structure size.
Depending on the ABI. Check overlapping.
Limitations: none.
PR: none.
Originator:
www.eeworm.com/read/100077/15886249
readme
memmove() is a very, very fast non-overlapping memory copy, but
since it does not save certain registers it uses, calling from
GCC can be tricky. GCC does a fabulous job of grinding all it
can out of
www.eeworm.com/read/438449/7731090
c ga_access.c
#include "ga.h"
/* ga_access and release do not protect against overlapping access. Use a
common mutex to guard such uses */
/* ?? is a lock needed at all? */
int ga_access( GA ga, void *buf )
{