# Internal data representation changes in GIT version

**URL:** <https://swi-prolog.discourse.group/t/internal-data-representation-changes-in-git-version/7355>\
**Category:** Announce\
**Created:** [April 6, 2024, 4:51pm UTC](https://swi-prolog.discourse.group/t/internal-data-representation-changes-in-git-version/7355 "2024-04-06T16:51:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jan](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jan/32/4_2.png) [@jan](https://swi-prolog.discourse.group/u/jan)\
**Post date:** [April 6, 2024, 4:51pm UTC](https://swi-prolog.discourse.group/t/internal-data-representation-changes-in-git-version/7355/1 "2024-04-06T16:51:36Z")

</div>

The changes announced with [Cooking: internal data representation](https://swi-prolog.discourse.group/t/cooking-internal-data-representation/7351) have been pushed to the `swipl-devel.git` `master` branch.

> Users should be aware that internally a lot has changed. The commits affect nearly 4,000 lines spread over 115 files. Unfortunately, while all tests pass, **some regression is to be expected**. Please **test and report issues**

### Consequences

- The QLF format is incompatible. You may have to delete old `*.qlf` files from the build directory if you do an incremental build. You can do so by running this in the build directory:

- The 64 bit version should be fully compatible

- On 32 bit version (still distributed for Windows, can be build on small embedded Linux systems such as Raspberry Pi (although these also move to 64 bits) and the WASM version) there are a few more consequences:

### Next steps

Timing for the next steps is still unclear. Assuming these changes hold, several steps come into view. For example:

- Get rid of relative addressing for Prolog data. That almost surely will improve performance. It will also simplify the garbage collector and allows for Prolog data that does not live on the stack of the running engine. Think about shared ground data or allow _engines_ to access each others data.
- Simplify the data type tags. That should simplify the system and improve performance.
- Consider using 32 bit VM instructions on 64 bit hardware. That would seriously reduce the size of compiled code on 64 bit machines.
