all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Perry E. Metzger" <perry@piermont.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: "Eric S. Raymond" <esr@snark.thyrsus.com>, emacs-devel@gnu.org
Subject: Re: Defending GCC considered futile
Date: Mon, 9 Feb 2015 17:04:54 -0500	[thread overview]
Message-ID: <20150209170454.6f653135@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <877fvt73su.fsf@mid.deneb.enyo.de>

On Sat, 07 Feb 2015 23:30:25 +0100 Florian Weimer <fw@deneb.enyo.de>
wrote:
> * Eric S. Raymond:
> 
> > I'm pretty sure this is not true.  If the clang/LLVM people decide
> > they want to eat GCC's lunch, they *will* do it.  The reason has
> > nothing to do with any philosophical issue but merely the fact
> > that compiler technology has advanced significantly in ways that
> > GCC is not well positioned to exploit.  The clang/LLVM people
> > have both a clean-sheet technology advantage
> 
> LLVM was first relased in 2003, Clang was opened up in 2007 (but is
> likely a bit older).  Those aren't young projects by any standard,
> and I doubt their sheets are particularly clean by this point.

Speaking as someone who works inside LLVM a bunch: the LLVM people
are fanatical, absolutely fanatical, about refactoring and keeping
their architecture clean. The whole thing is kept extremely modular,
very easily modified, very well documented. LLVM *is* clean. It is, in
fact, architecturally beautiful. I wish it wasn't written in C++, and
the AST format seems unnecessarily complicated to me, but that aside,
I have few complaints.

Perry
-- 
Perry E. Metzger		perry@piermont.com



  parent reply	other threads:[~2015-02-09 22:04 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07 20:29 Defending GCC considered futile Eric S. Raymond
2015-02-07 21:24 ` David Kastrup
2015-02-09  0:04   ` Richard Stallman
2015-02-07 22:30 ` Florian Weimer
2015-02-08 14:12   ` Stefan Monnier
2015-02-09 19:39     ` Florian Weimer
2015-02-09 22:04   ` Perry E. Metzger [this message]
2015-02-09  0:04 ` Richard Stallman
2015-02-09  4:13   ` Stefan Monnier
2015-02-09  5:50   ` Stephen J. Turnbull
2015-02-09 22:06     ` Richard Stallman
2015-02-09 22:24       ` Perry E. Metzger
2015-02-10  3:37         ` Eli Zaretskii
2015-02-10  8:30           ` Daniel Colascione
2015-02-10  8:47             ` Helmut Eller
2015-02-10 15:58               ` Eli Zaretskii
2015-02-10 15:57             ` Eli Zaretskii
2015-02-10 18:19               ` Daniel Colascione
2015-02-10 18:41                 ` David Kastrup
2015-02-10 19:27                   ` Eli Zaretskii
2015-02-10 19:23                 ` Eli Zaretskii
2015-02-10 20:05                   ` David Kastrup
2015-02-10 23:14                   ` Stefan Monnier
2015-02-11  3:46                     ` Eli Zaretskii
2015-02-11 23:11                     ` Richard Stallman
2015-02-10 22:48         ` Richard Stallman
2015-02-11  2:08           ` John Yates
2015-02-11 15:42           ` Perry E. Metzger
2015-02-11 16:14             ` Eli Zaretskii
2015-02-11 16:29               ` Perry E. Metzger
2015-02-11 16:44                 ` Eli Zaretskii
2015-02-11 16:54                   ` Eli Zaretskii
2015-02-11 20:50                     ` Perry E. Metzger
2015-02-12  3:37                       ` Eli Zaretskii
2015-02-12  3:54                         ` Perry E. Metzger
2015-02-11 19:14                 ` Florian Weimer
2015-02-11 19:19                 ` Stefan Monnier
2015-02-11 23:13                 ` Richard Stallman
2015-02-12  1:48               ` raman
2015-02-11 23:13             ` Richard Stallman
2015-02-09  7:41   ` Helmut Eller
2015-02-09 19:30   ` Florian Weimer
2015-02-09 22:41     ` Perry E. Metzger
2015-02-10 22:46     ` Richard Stallman
2015-02-09 22:19   ` Perry E. Metzger

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=20150209170454.6f653135@jabberwock.cb.piermont.com \
    --to=perry@piermont.com \
    --cc=emacs-devel@gnu.org \
    --cc=esr@snark.thyrsus.com \
    --cc=fw@deneb.enyo.de \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.