From: Vasudev Kamath <vasudev@copyninja.info>
To: Ramakrishnan Muthukrishnan <ram@rkrishnan.org>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Undefined Behaviour in C
Date: Mon, 23 Nov 2015 16:50:46 +0530 [thread overview]
Message-ID: <87egfhotbl.fsf@copyninja.info> (raw)
In-Reply-To: <1448274004.1751482.447419065.2BE466C4@webmail.messagingengine.com> (Ramakrishnan Muthukrishnan's message of "Mon, 23 Nov 2015 15:50:04 +0530")
Ramakrishnan Muthukrishnan <ram@rkrishnan.org> writes:
> Had been reading the SOSP paper:
> <https://pdos.csail.mit.edu/papers/stack:sosp13.pdf>
>
> and this blog post that proposes a simpler C:
> <http://blog.regehr.org/archives/1180>
I started reading the paper and its interesting. I didn't knew till date
how optimizations really worked and why they were considered harmful.
Yet to read the blog.
> I wonder how Plan 9 C compiler, which is a non-ANSI compliant compiler,
> treats those parts that the ANSI C standard treats as undefined.
No idea. But Brantley Coile might be able to answer, most of his article
he mentions compiler won't do any magic, I assume those magic are meant
for the optimizations.
Of course others from 9fans/9front might have answers but that name came
to my mind as I read some recent article where he mentioned about plan9
compilers.
next prev parent reply other threads:[~2015-11-23 11:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 10:20 Ramakrishnan Muthukrishnan
2015-11-23 11:20 ` Vasudev Kamath [this message]
2015-11-25 10:27 ` Alexandru Gheorghe
2015-11-25 10:43 ` Brantley Coile
2015-11-25 10:53 ` Brantley Coile
2015-11-25 12:59 ` Charles Forsyth
2015-11-25 13:48 ` erik quanstrom
2015-11-25 14:25 ` Brantley Coile
2015-11-25 14:31 ` Brantley Coile
2015-11-25 16:03 ` plannine
2015-11-25 17:13 ` Ryan Gonzalez
2015-11-25 18:41 ` Brantley Coile
2015-11-26 2:04 ` Prof Brucee
2015-11-26 2:43 ` Brantley Coile
2015-11-26 2:57 ` Prof Brucee
2015-11-26 3:48 ` Ryan Gonzalez
2015-11-26 7:27 ` Bakul Shah
2015-11-26 11:22 ` Brantley Coile
2015-11-26 11:37 ` tlaronde
2015-11-26 11:55 ` Charles Forsyth
2015-11-26 11:38 ` Bruce Ellis
2015-11-26 16:31 ` erik quanstrom
2015-11-26 16:42 ` Brantley Coile
2015-11-26 16:50 ` Charles Forsyth
2015-11-26 17:12 ` erik quanstrom
2015-11-26 16:46 ` Alexandru Gheorghe
2015-11-26 17:48 ` Bakul Shah
2015-11-26 18:04 ` Brantley Coile
2015-11-26 23:14 ` Steve Simon
2015-11-26 23:24 ` Charles Forsyth
2015-11-26 23:55 ` Brantley Coile
2015-11-25 19:19 ` Steffen Nurpmeso
2015-11-23 11:32 ` Charles Forsyth
2015-11-23 11:37 ` Charles Forsyth
2015-11-23 11:50 ` Brantley Coile
2015-11-23 12:05 ` Charles Forsyth
2015-11-23 12:17 ` Brantley Coile
2015-11-23 12:40 ` Charles Forsyth
2015-11-23 12:09 ` Charles Forsyth
2015-11-23 14:30 ` Charles Forsyth
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=87egfhotbl.fsf@copyninja.info \
--to=vasudev@copyninja.info \
--cc=9fans@9fans.net \
--cc=ram@rkrishnan.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).