Linux toolchain discussions
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	linux-toolchains@vger.kernel.org, peterz@infradead.org,
	rostedt@goodmis.org, gregkh@linuxfoundation.org,
	keescook@chromium.org
Subject: Re: A few proposals from the C standards committee
Date: Wed, 24 Jan 2024 06:58:26 -0800	[thread overview]
Message-ID: <99fac1e2-856d-4e05-abc5-e756b9cc3827@paulmck-laptop> (raw)
In-Reply-To: <CAHk-=wid0xiN8a0=ixi3CyyZstcVnUqPXAMjethOxvXw1LjSuQ@mail.gmail.com>

On Tue, Jan 23, 2024 at 12:24:44PM -0800, Linus Torvalds wrote:
> On Tue, 23 Jan 2024 at 12:19, H. Peter Anvin <hpa@zytor.com> wrote:
> >
> > > n3203 Strict order of expression evaluation
> > >       I do like it.  The 1980s were over a long time ago.
> >
> > The question is: is this going to wreck havoc with performance. The C++
> > reference implies it won't, though.
> 
> Well, they also had numbers from an actual implementation showing that
> it didn't (ie "win some, lose some").
> 
> The "ordering is undefined" is, I think, almost entirely an effect of
> "compilers weren't that smart, and implementations differed".
> 
> So I'd love for sequence points to go away. They are one of the more
> subtle parts of C, and I do not believe that they have any real
> advantage any more.
> 
> (And by "go away" I obviously mean "everything is a sequence point",
> not "nothing is a sequence point" - so they'd go away as a concept,
> because they'd become a non-issue).

Agreed, and here is hoping!

							Thanx, Paul

  reply	other threads:[~2024-01-24 14:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 16:46 A few proposals from the C standards committee Paul E. McKenney
2024-01-23 18:58 ` Linus Torvalds
2024-01-23 20:00   ` Paul E. McKenney
2024-01-23 20:20     ` Linus Torvalds
2024-01-23 20:35       ` Jakub Jelinek
2024-01-23 20:43         ` Linus Torvalds
2024-01-23 20:46           ` H. Peter Anvin
2024-01-24 13:46             ` Paul E. McKenney
2024-01-25 13:00           ` Paul E. McKenney
2024-01-24 13:16         ` Paul E. McKenney
2024-01-23 20:44       ` H. Peter Anvin
2024-01-24 12:52       ` Paul E. McKenney
2024-01-23 20:39     ` Linus Torvalds
2024-01-23 22:35   ` Martin Uecker
2024-01-23 20:16 ` H. Peter Anvin
2024-01-23 20:24   ` Linus Torvalds
2024-01-24 14:58     ` Paul E. McKenney [this message]
2024-01-25 12:52   ` Paul E. McKenney
2024-01-23 22:39 ` Kees Cook

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=99fac1e2-856d-4e05-abc5-e756b9cc3827@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=linux-toolchains@vger.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