This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | steve.dower |
|---|---|
| Recipients | christian.heimes, paul.moore, steve.dower, tim.golden, vstinner, zach.ware |
| Date | 2016年09月13日.13:45:18 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1473774318.82.0.0882833139392.issue28126@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Yes, memcpy (or preferably memcpy_s, which includes the size of the destination) are basically intrinsics that will inline short copies and call out to a range of implementations depending on alignment/overlap/etc. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016年09月13日 13:45:18 | steve.dower | set | recipients: + steve.dower, paul.moore, vstinner, christian.heimes, tim.golden, zach.ware |
| 2016年09月13日 13:45:18 | steve.dower | set | messageid: <1473774318.82.0.0882833139392.issue28126@psf.upfronthosting.co.za> |
| 2016年09月13日 13:45:18 | steve.dower | link | issue28126 messages |
| 2016年09月13日 13:45:18 | steve.dower | create | |