search for: cprcs

...does not conform to the standard when we have a few VFP registers available but not enough. In that case, the beginning members of HA will be allocated to VFP, and the rest will go on stack. To fix the problem, it will be great if we can let the backend know the HA will be on stack and later VPF CPRCs will be on stack as well. There are some discussions on this, at least from the comments in TargetInfo.cpp: // This assumption is optimistic, as there could be free registers available // when we need to pass this argument in memory, and LLVM could try to pass // the argument in the free register....

...when we have a few VFP registers available but not > enough. > > In that case, the beginning members of HA will be allocated to VFP, and the > rest will go on stack. > > To fix the problem, it will be great if we can let the backend know the HA > will be on stack and later VPF CPRCs will be on stack as well. > There are some discussions on this, at least from the comments in > TargetInfo.cpp: > // This assumption is optimistic, as there could be free registers available > // when we need to pass this argument in memory, and LLVM could try to pass > // the argume...

...the standard when we have a few VFP registers available but not enough. > > In that case, the beginning members of HA will be allocated to VFP, and the rest will go on stack. > > To fix the problem, it will be great if we can let the backend know the HA will be on stack and later VPF CPRCs will be on stack as well. > There are some discussions on this, at least from the comments in TargetInfo.cpp: > // This assumption is optimistic, as there could be free registers available > // when we need to pass this argument in memory, and LLVM could try to pass > // the argument in...

...en we have a few VFP registers available but not enough. >> >> In that case, the beginning members of HA will be allocated to VFP, and the rest will go on stack. >> >> To fix the problem, it will be great if we can let the backend know the HA will be on stack and later VPF CPRCs will be on stack as well. >> There are some discussions on this, at least from the comments in TargetInfo.cpp: >> // This assumption is optimistic, as there could be free registers available >> // when we need to pass this argument in memory, and LLVM could try to pass >> //...

...VFP registers available but not enough. >>> >>> In that case, the beginning members of HA will be allocated to VFP, and the rest will go on stack. >>> >>> To fix the problem, it will be great if we can let the backend know the HA will be on stack and later VPF CPRCs will be on stack as well. >>> There are some discussions on this, at least from the comments in TargetInfo.cpp: >>> // This assumption is optimistic, as there could be free registers available >>> // when we need to pass this argument in memory, and LLVM could try to pass...