bugfix of Tensor.copy with limits · Pull Request !91083 · MindSpore/mindspore

1. bugfix of Tensor.copy with limits
---
<!--  Thanks for sending a pull request!  Here are some tips for you:

1) If this is your first time, please read our contributor guidelines: https://gitee.com/mindspore/mindspore/blob/master/CONTRIBUTING.md

2) If you want to contribute your code but don't know who will review and merge, please add label `mindspore-assistant` to the pull request, we will find and do it as soon as possible.
-->

**What type of PR is this?**

/kind bug

---

**What does this PR do / why do we need it**:
当前Tensor.copy接口的实现方式不太合理，在int32/int64/uint32/uint64/complex64/complex128等数据类型下，都可能出现精度损失
- 使用数据搬移方式实现int32/int64/uint32/uint64的Tensor.copy
- 使用加法实现complex64/complex128的Tensor.copy
- 其余数据类型保持不变，修复可能出现的精度损失问题

**Which issue(s) this PR fixes**:

Fixes #IDAGZX

---

**Test Plan and Test result：What scenarios were tested, and what were the verification results（Function, performance, reliability, etc.）**：
- 新增用例看护极限数值场景：tests/st/tensor/test_copy.py
- 验证截图：![输入图片说明](https://foruda.gitee.com/images/1765354748688463094/bdbb02ed_12329485.png "屏幕截图")

**Self-checklist**:（**请自检，在[ ]内打上x，我们将检视你的完成情况，否则会导致pr无法合入**）

+ - [x] **设计**：PR对应的方案是否已经经过Maintainer评审，方案检视意见是否均已答复并完成方案修改
+ - [x] **测试**：PR中的代码是否已有UT/ST测试用例进行充分的覆盖，新增测试用例是否随本PR一并上库或已经上库
+ - [x] **验证**：PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述
+ - [x] **接口**：是否涉及对外接口变更，相应变更已得到接口评审组织的通过，API对应的注释信息已经刷新正确
+ - [x] **文档**：是否涉及官网文档修改，如果涉及请及时提交资料到Doc仓

GVP MindSpore/mindspore
关闭

发现个问题

GVPMindSpore/mindspore关闭

搜索帮助

GVP MindSpore/mindspore
关闭