From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] kencc benchmark vs gcc
Date: Tue, 21 Oct 2014 13:17:05 +1100 [thread overview]
Message-ID: <CAJQxxw=xbORc2tzEgKTE_sd_S2uQpzAyvX_=LWF=gRj96F3mOQ@mail.gmail.com> (raw)
In-Reply-To: <3E158C11-6ABE-452F-9400-BFA877CEE85D@9srv.net>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
Then again if I'm writing a multi-threaded program then go blows gcc out of
the water.
brucee
On 18/10/2014 8:18 AM, "Anthony Sorace" <a@9srv.net> wrote:
> There have been many over the years (I think the original papers present
> something), but I've not seen anything current enough to be useful. The
> very short version: gcc almost always produces faster executables from the
> same code.
>
>
>
[-- Attachment #2: Type: text/html, Size: 664 bytes --]
prev parent reply other threads:[~2014-10-21 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 19:56 Yoann Padioleau
2014-10-17 20:24 ` Anthony Sorace
2014-10-21 2:17 ` Bruce Ellis [this message]
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='CAJQxxw=xbORc2tzEgKTE_sd_S2uQpzAyvX_=LWF=gRj96F3mOQ@mail.gmail.com' \
--to=bruce.ellis@gmail.com \
--cc=9fans@9fans.net \
/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).