From: Florian Weimer <fw@deneb.enyo.de>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Defending GCC considered futile
Date: Wed, 11 Feb 2015 20:14:56 +0100 [thread overview]
Message-ID: <87r3twmf9r.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20150211112941.148f783d@jabberwock.cb.piermont.com> (Perry E. Metzger's message of "Wed, 11 Feb 2015 11:29:41 -0500")
* Perry E. Metzger:
> On Wed, 11 Feb 2015 18:14:17 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> Modularizing GCC is not discouraged. It actually happens as we
>> speak, check out the latest developments in GCC 5 and GDB.
>
> If this is the case, what is the problem with Emacs directly linking
> against the GCC front end to get access to the C and C++ AST?
The C front end does not produce an AST, it lowers immediately to
GENERIC, whose only control flow constructs are conditional
expressions and gotos. The C++ front end extends GENERIC with
additional trees, preserving more information, but I do not know if it
is sufficiently complete to qualify as an AST.
I don't know if this can be fixed so that the result is still
maintainable and there is no observable speed difference no matter
what compiler flags you use.
(I looked at this because I wanted to introduce syntax-driven
unreachable code warnings, including a switch-case fallthrough
warning.)
next prev parent reply other threads:[~2015-02-11 19:14 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3twmf9r.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).