From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15653 invoked by alias); 16 Mar 2012 15:17:29 -0000 Received: (qmail 15640 invoked by uid 22791); 16 Mar 2012 15:17:27 -0000 X-SWARE-Spam-Status: No, hits=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail4-relais-sop.national.inria.fr (HELO mail4-relais-sop.national.inria.fr) (192.134.164.105) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 16 Mar 2012 15:17:13 +0000 Received: from unknown (HELO pluto) ([193.50.110.167]) by mail4-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 16 Mar 2012 16:17:12 +0100 From: ludovic.courtes@inria.fr (Ludovic =?iso-8859-1?Q?Court=E8s?=) To: Richard Guenther Cc: Ian Lance Taylor , Andrew Pinski , gcc@gcc.gnu.org Subject: Re: GCC 4.7.0RC: Mangled names in cc1 References: <877gyu85mc.fsf@inria.fr> <87ty1y6oq2.fsf@inria.fr> <877gytvl0o.fsf@inria.fr> <87r4x1r9re.fsf@inria.fr> <87pqciurih.fsf@inria.fr> <87obrwyfhg.fsf@inria.fr> <87ty1ou26x.fsf@inria.fr> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 27 =?iso-8859-1?Q?Vent=F4se?= an 220 de la =?iso-8859-1?Q?R=E9volution?= X-PGP-Key-ID: 0xEA52ECF4 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 83C4 F8E5 10A3 3B4C 5BEA D15D 77DD 95E2 EA52 ECF4 X-OS: x86_64-unknown-linux-gnu Date: Fri, 16 Mar 2012 15:17:00 -0000 In-Reply-To: (Richard Guenther's message of "Fri, 16 Mar 2012 14:08:21 +0100") Message-ID: <87mx7gshhk.fsf@inria.fr> User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.93 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2012-03/txt/msg00251.txt.bz2 Hello, Richard Guenther skribis: > 2012/3/16 Ludovic Court=C3=A8s : [...] > Well, if you invent new paradigms Hmm, I didn=E2=80=99t invent anything here. > in your plugin that are not used by GCC itself but use GCC internals > (which all plugins have to do ...) then I know where the problem lies > ;) I suppose you would be better served by some of the more high-level > plugin packages that let you write GCC plugins in python or lisp? Sure, even Guile-GCC [0]. :-) (Speaking of which, since it mostly uses Guile=E2=80=99s dynamic FFI to interface with GCC, and thus dlsyms GCC=E2=80=99s symbols, it will also suf= fer from the transition. How does the Python plug-in handle that? Is it written in ANSI C, or does it use ctypes?) Nevertheless, I found that GNU C provides a nice middle ground. > Or wait until GCC has fully transitioned to C++ (at least I expect we won= 't > ever relax the rule that GCC can be built with a C++ compiler) and use > C++0x lambdas. That would be great, but I=E2=80=99d like to support 4.5 and 4.6 as well. Thanks, Ludo=E2=80=99. [0] https://gitorious.org/guile-gcc/guile-gcc