From: Jakub Jelinek <jakub@redhat.com>
To: Marco Elver <elver@google.com>
Cc: paulmck@kernel.org, linux-toolchains@vger.kernel.org,
peterz@infradead.org, hpa@zytor.com, rostedt@goodmis.org,
gregkh@linuxfoundation.org, keescook@chromium.org,
torvalds@linux-foundation.org,
Evgenii Stepanov <eugenis@google.com>,
Kostya Serebryany <kcc@google.com>
Subject: Re: A few proposals, this time from the C++ standards committee
Date: Tue, 19 Mar 2024 09:07:16 +0100 [thread overview]
Message-ID: <ZflHtJDMhk5Ru8Du@tucnak> (raw)
In-Reply-To: <CANpmjNOJTzMzi6aNevn=ruF_yxeYez=D-+qBg8OKVT3dbokRtg@mail.gmail.com>
On Tue, Mar 19, 2024 at 08:41:27AM +0100, Marco Elver wrote:
> Hi Paul,
>
> On Sun, 17 Mar 2024 at 10:14, Paul E. McKenney <paulmck@kernel.org> wrote:
> > ------------------------------------------------------------------------
> [...]
> > D3125R0 — Pointer tagging
> > Another one that is late to the party, and thus not yet formally
> > published. The idea is to provide a way to access pointer bits
> > that are not relevant to pointer dereferencing for pointers to
> > properly aligned objects or that are unused high-order bits.
> > It would be nice. The devil is in the details.
>
> You mention it's not formally published, but is there a draft that is
> already accessible somewhere?
https://wg21.link/D3125R0
Jakub
next prev parent reply other threads:[~2024-03-19 8:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 9:14 A few proposals, this time from the C++ standards committee Paul E. McKenney
2024-03-17 18:50 ` Linus Torvalds
2024-03-17 20:56 ` Paul E. McKenney
2024-03-17 20:50 ` Linus Torvalds
2024-03-17 21:04 ` Paul E. McKenney
2024-03-17 21:44 ` Linus Torvalds
2024-03-17 22:02 ` Paul E. McKenney
2024-03-17 22:34 ` Linus Torvalds
2024-03-17 23:46 ` Jonathan Martin
2024-03-18 0:42 ` Paul E. McKenney
2024-03-18 1:49 ` Linus Torvalds
2024-03-18 2:44 ` Paul E. McKenney
2024-03-18 2:57 ` Randy Dunlap
2024-03-18 4:42 ` Paul E. McKenney
2024-03-18 4:45 ` Randy Dunlap
2024-03-18 16:32 ` Linus Torvalds
2024-03-18 16:48 ` H. Peter Anvin
2024-03-19 7:41 ` Marco Elver
2024-03-19 8:07 ` Jakub Jelinek [this message]
2024-06-05 13:52 ` Paul E. McKenney
2024-06-05 18:08 ` Linus Torvalds
2024-06-05 18:24 ` Linus Torvalds
2024-06-05 19:16 ` Paul E. McKenney
2024-06-05 19:12 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZflHtJDMhk5Ru8Du@tucnak \
--to=jakub@redhat.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kcc@google.com \
--cc=keescook@chromium.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).