From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Alexandre Oliva <oliva@gnu.org>
Cc: "Eric S. Raymond" <esr@thyrsus.com>, <gcc@gcc.gnu.org>,
<emacs-devel@gnu.org>
Subject: Re: clang and FSF's strategy
Date: Thu, 23 Jan 2014 18:21:13 +0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1401231809110.31884@digraph.polyomino.org.uk> (raw)
In-Reply-To: <oreh40q1q3.fsf@livre.home>
On Tue, 21 Jan 2014, Alexandre Oliva wrote:
> On Jan 21, 2014, esr@thyrsus.com (Eric S. Raymond) wrote:
>
> > I think it is time to question whether the anti-plugins policy is
> > still the best way to accomplish this.
>
> Err... Excuse me, but what anti-plugins policy are you talking about?
Indeed.
There are people working right now on improvements to modularity in GCC,
elimination of global state, and support for use of GCC in a JIT library,
led by Andrew MacLeod and David Malcolm. Contributions to those sorts of
efforts (and to the plugin interface) are more useful than rhetoric. No
policy objections are being made to these patches, it's simply a matter of
the work involved. If people want suggestions that don't conflict with
what Andrew and David are working on, a couple of suggestions:
* We have about 700 target macros (my script lists 697 right now, but
there are likely some false positives, and maybe false negatives), all of
which should move to the hooks mechanism to enable multiple targets to be
supported in a single compiler binary, and to get other benefits such as
not having the build of GCC fail with warnings seen only for some targets
because of differences in the target macro definitions. I expect a large
proportion of these (not used in #if or in code built for the target,
etc.) could be converted to hooks using some form of script-based
automatic refactoring, possibly with manual fine-tuning of the resulting
patches.
* Andrew MacLeod's plans for improving static typing are I think largely
about the middle end - there is plenty of scope for improving static
typing of datastructures used in the front ends, and cleanly separating
them from the language-independent compiler as far as possible.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-01-23 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 20:19 clang and FSF's strategy Eric S. Raymond
2014-01-22 0:07 ` David Kastrup
2014-01-25 15:26 ` David Kastrup
2014-01-22 0:50 ` Alexandre Oliva
2014-01-23 18:21 ` Joseph S. Myers [this message]
2014-01-22 1:31 ` Stefan Monnier
2014-01-22 1:31 ` Ian Lance Taylor
2014-01-22 4:02 ` Eric S. Raymond
2014-01-22 11:27 ` David Kastrup
2014-01-22 14:33 ` Jordi Gutiérrez Hermoso
2014-01-23 10:03 ` Michael Witten
2014-01-23 10:52 ` David Kastrup
2014-01-23 17:17 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2014-01-22 4:49 grischka
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=Pine.LNX.4.64.1401231809110.31884@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
--cc=gcc@gcc.gnu.org \
--cc=oliva@gnu.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.
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.