From: Toon Moene <toon@moene.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
parallel@lists.isocpp.org, llvm-dev@lists.llvm.org,
Will Deacon <will.deacon@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
Luc Maranget <luc.maranget@inria.fr>,
Andrew Morton <akpm@linux-foundation.org>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [isocpp-parallel] Proposal for new memory_order_consume definition
Date: Mon, 29 Feb 2016 21:45:28 +0100 [thread overview]
Message-ID: <56D4ADE8.7090403@moene.org> (raw)
In-Reply-To: <CA+55aFyauwKmUdxfrKcy5Q2kvdej5fWt6xL+amVyPFhzmHMcsg@mail.gmail.com>
On 02/28/2016 05:13 PM, Linus Torvalds wrote:
> Yeah, let's just say that the original C designers were
> better at their job than a gaggle of standards people who were making
> bad crap up to make some Fortran-style programs go faster.
The original C designers were defining a language that would make it
easy to write operating systems in (and not having to rely on assembler).
I misled the quote where they said they first tried Fortran (and
concluded it didn't fit their purpose).
BTW, Fortran was designed around floating point arithmetic (and its
non-relation to the mathematical concept of the field of the reals).
It used integers only for counting and indexing arrays, so it had no
purpose for "signed integers that overflowed". Therefore, to the Fortran
standard, this was "undefined". It was literally "undefined" - as it was
not described by the standard's text.
--
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news
next prev parent reply other threads:[~2016-02-29 20:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 1:10 Proposal for new memory_order_consume definition Paul E. McKenney
2016-02-20 2:15 ` [isocpp-parallel] " Tony V E
2016-02-20 19:53 ` Paul E. McKenney
2016-02-26 0:46 ` Hans Boehm via llvm-dev
2016-02-26 23:56 ` Lawrence Crowl
2016-02-27 17:06 ` Paul E. McKenney
2016-02-27 19:16 ` Linus Torvalds via llvm-dev
2016-02-27 23:10 ` Paul E. McKenney via llvm-dev
2016-02-27 23:10 ` Paul E. McKenney
2016-02-28 8:27 ` Markus Trippelsdorf via llvm-dev
2016-02-28 8:27 ` Markus Trippelsdorf
2016-02-28 16:13 ` Linus Torvalds
2016-02-28 16:50 ` via llvm-dev
2016-02-28 16:50 ` [llvm-dev] " cbergstrom
2016-02-29 17:37 ` Michael Matz
2016-02-29 17:57 ` Linus Torvalds via llvm-dev
2016-02-29 17:57 ` Linus Torvalds
2016-02-29 19:38 ` Lawrence Crowl
2016-02-29 21:10 ` James Y Knight via llvm-dev
2016-02-29 21:12 ` James Y Knight via llvm-dev
2016-02-29 21:12 ` [llvm-dev] " James Y Knight
2016-02-29 20:45 ` Toon Moene [this message]
2016-02-29 20:45 ` Toon Moene
2016-02-29 18:17 ` Michael Matz
2016-03-01 1:28 ` Paul E. McKenney via llvm-dev
2016-03-01 1:28 ` 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=56D4ADE8.7090403@moene.org \
--to=toon@moene.org \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm-dev@lists.llvm.org \
--cc=luc.maranget@inria.fr \
--cc=markus@trippelsdorf.de \
--cc=mingo@kernel.org \
--cc=parallel@lists.isocpp.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
/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).