From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] Unix stories
Date: Wed, 4 Jan 2017 11:58:41 -0500 [thread overview]
Message-ID: <017201d266ab$cda885a0$68f990e0$@ronnatalie.com> (raw)
In-Reply-To: <1483548842.1612851.837252537.064CFDA2@webmail.messagingengine.com>
There's a trademark between allowing the compiler to reorder things and having a defined order of operations.
Steps like that are well-defined in Java for instance. C lets the compiler do what it sees fit.
Note that it's not necessarily any better in assembler. There are RISC architectures where load-followed-by-store and vice versa may not always be valid if done in quick succession. Requiring the compiler to insert sequence points typically wastes a lot of cycles. Assembler programmers tend to think about what they are doing, the C compiler tries to do some of this on its own and its not clairvoyant.
next prev parent reply other threads:[~2017-01-04 16:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 5:00 Larry McVoy
2017-01-01 6:48 ` Nick Downing
2017-01-02 2:03 ` Steve Johnson
2017-01-02 2:42 ` Nick Downing
2017-01-02 6:01 ` Steve Nickolas
2017-01-02 6:21 ` Warren Toomey
2017-01-02 6:25 ` Nick Downing
2017-01-04 4:07 ` Steve Nickolas
2017-01-02 7:29 ` arnold
2017-01-02 22:52 ` Dave Horsfall
2017-01-02 22:56 ` Larry McVoy
2017-01-02 22:59 ` Ronald Natalie
2017-01-02 22:58 ` Ronald Natalie
2017-01-02 23:23 ` Tim Bradshaw
2017-01-03 0:49 ` Larry McVoy
2017-01-03 11:36 ` Joerg Schilling
2017-01-04 13:04 ` Steffen Nurpmeso
2017-01-04 14:07 ` Random832
2017-01-04 14:54 ` Ron Natalie
2017-01-04 15:59 ` Random832
2017-01-04 16:30 ` Steffen Nurpmeso
2017-01-04 16:32 ` Random832
2017-01-04 16:51 ` Steffen Nurpmeso
2017-01-04 16:54 ` Random832
2017-01-04 16:58 ` Ron Natalie [this message]
2017-01-04 17:38 ` Steffen Nurpmeso
2017-01-04 17:47 ` Steffen Nurpmeso
2017-01-04 18:51 ` Steve Johnson
2017-01-04 17:08 ` Steffen Nurpmeso
2017-01-04 16:22 ` Steffen Nurpmeso
2017-01-04 16:35 ` Random832
2017-01-04 17:03 ` Steffen Nurpmeso
2017-02-09 13:46 ` Steffen Nurpmeso
2017-02-09 14:55 ` Random832
2017-02-09 17:15 ` Steffen Nurpmeso
2017-01-01 13:11 ` Ron Natalie
2017-01-01 16:50 Noel Chiappa
2017-01-01 21:45 ` Nemo
2017-01-02 2:53 ` Wesley Parish
2017-01-02 14:30 Doug McIlroy
2017-01-02 18:36 ` Dan Cross
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='017201d266ab$cda885a0$68f990e0$@ronnatalie.com' \
--to=ron@ronnatalie.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).