Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spans supporting pointer-sized sizes (e.g. 64 bit on 64 bit OS) #13533

Open
lostmsu opened this issue Oct 4, 2019 · 1 comment
Open

Spans supporting pointer-sized sizes (e.g. 64 bit on 64 bit OS) #13533

lostmsu opened this issue Oct 4, 2019 · 1 comment
Labels
area-System.Runtime backlog-cleanup-candidate An inactive issue that has been marked for automated closure. enhancement Product code improvement that does NOT require public API changes/additions no-recent-activity
Milestone
Future

Comments

@lostmsu
Copy link

lostmsu commented Oct 4, 2019

This is very related to https://github.com/dotnet/coreclr/issues/23132 (but not the same).

Currently Span Length is limited to just under Int32.MaxValue.

This is problematic when working on relatively large data, as we have to resort to working with raw pointers and unmanaged memory allocation to work with contiguous arrays of 2G+ elements.

To give a concrete example, from .NET I can't simply give TensorFlow 800_000 64x64 1-channel (channel==byte) images as a contiguous array.
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the 5.0 milestone Jan 31, 2020
@maryamariyan maryamariyan added the untriaged New issue has not been triaged by the area owner label Feb 26, 2020
@joperezr joperezr added enhancement Product code improvement that does NOT require public API changes/additions and removed untriaged New issue has not been triaged by the area owner labels Jul 7, 2020
@joperezr joperezr modified the milestones: 5.0.0, Future Jul 7, 2020
@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@dotnet-policy-service dotnet-policy-service bot added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-System.Runtime backlog-cleanup-candidate An inactive issue that has been marked for automated closure. enhancement Product code improvement that does NOT require public API changes/additions no-recent-activity
Projects
None yet
Milestone
Future
Development

No branches or pull requests
4 participants
@lostmsu @maryamariyan @msftgits @joperezr