[libcxx-commits] [clang] [libcxx] [clang & libcxx] constexpr pointer tagging (DO NOT MERGE) (PR #111861)

Corentin Jabot via libcxx-commits libcxx-commits at lists.llvm.org
Fri Oct 16 01:10:53 PDT 2026


Hana =?utf-8?q?Dusíková?= <hanicka at hanicka.net>,
Hana =?utf-8?q?Dusíková?= <hanicka at hanicka.net>,
Hana =?utf-8?q?Dusíková?= <hanicka at hanicka.net>,
Hana =?utf-8?q?Dusíková?= <hanicka at hanicka.net>,
Hana =?utf-8?q?Dusíková?= <hanicka at hanicka.net>,
Hana =?utf-8?q?Dusíková?= <hanicka at hanicka.net>,
Hana =?utf-8?q?Dusíková?= <hanicka at hanicka.net>,
Hana =?utf-8?q?Dusíková?= <hanicka at hanicka.net>,
Hana =?utf-8?q?Dusíková?= <hanicka at hanicka.net>
Message-ID:
In-Reply-To: <llvm.org/llvm/llvm-project/pull/111861 at github.com>


cor3ntin wrote:

@smallp-o-p @ldionne We can certainly review the language changes. 

The only concern is that the feature might change, so it should not be stabilized, but the changes should not impact the compiler side of things.

@hanickadot For ease of review, can you separate the Clang changes in a separate PR
@tbaederr I'm assuming we will need an interpreter implementation?

I have no clue if we prefer the builtins approach over a magic attribute that would preserve pointer information in the APValue. Do we have any idea what GCC plans are?

In any case, do we need `__builtin_tag_pointer_mask_as_int` ?

https://github.com/llvm/llvm-project/pull/111861


More information about the libcxx-commits mailing list