Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 770187
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T18:27:30+00:00 2026-05-14T18:27:30+00:00

In F#, there’s the NativePtr module, but it seems to only support 32 bit

  • 0

In F#, there’s the NativePtr module, but it seems to only support 32 bit offsets for its’ add/get/set functions, just like System.IntPtr does.

Is there a way to add a 64 bit offset to a native pointer (nativeptr<‘a>) in F#? Of course I could convert all addresses to 64 bit integers, do normal integer operations and then convert the result again to nativeptr<‘a>, but this would cost additional add and imul instructions. I really want the AGUs to perform the address calculations.

For instance, using unsafe in C# you could do something like

void* ptr = Marshal.AllocHGlobal(...).ToPointer();
int64 offset = ...;
T* newAddr = (T*)ptr + offset; // T has to be an unmanaged type

Well actually you can’t, because there is no “unmanaged” constraint for type parameters, but at least you can do general pointer arithmetic in a non-generic way.

In F# we finally got the unmanaged constraint; but how do I do the pointer arithmetic?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T18:27:31+00:00Added an answer on May 14, 2026 at 6:27 pm

    I’m not an expert in this field, but I took a look at the F# implementation of the NativePtr module and I think that there is no performance overhead associated with converting nativeptr<'a> to nativeint and back.

    The implementation uses inline IL and the inline IL code doesn’t contain any code – it is there just to make the F# compiler think that the value on the stack has a different type:

    let inline ofNativeInt (x:nativeint)    = (# "" x : nativeptr<_> #)
    let inline toNativeInt (x:nativeptr<_>) = (# "" x : nativeint    #)
    

    In fact, the NativePtr.add method also uses these two methods – it converts the pointer to nativeint and then adds the 32bit integer (multiplied by the size of the 'a type).

    So, the following function should be fine:

    let inline addNativeInt (x:nativeptr<'a>) (n:nativeint) : nativeptr<'a> = 
       (NativePtr.toNativeInt x) + n |> NativePtr.ofNativeInt
    

    All functions used in the code should be inlined, so you’ll end up with just a single instruction for addition (though, I have not verified that). You don’t even have to worry about using the function multiple times in your code (you can work with nativeptr<'a> all the time and use this function for addition).

    However, partitioning data may also be an option – as far as I know, the MSR team that was using F# for processing some large (>2GB) data sets used exactly this approach – they partitioned the data into 2GB blocks (stored in arrays).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

There are a few ways to get class-like behavior in javascript, the most common
There is a conversion process that is needed when migrating Visual Studio 2005 web
There are two weird operators in C#: the true operator the false operator If
There are two popular closure styles in javascript. The first I call anonymous constructor
There is previous little on the google on this subject other than people asking
There seem to be many ways to define singletons in Python. Is there a
There are numerous Agile software development methods. Which ones have you used in practice
There are several types of objects in a system, and each has it's own
There is a field in my company's Contacts table. In that table, there is
There are numerous libraries providing Linq capabilities to C# code interacting with a MySql

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.