From: Basile Starynkevitch <basile@starynkevitch.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 4.7.0RC: Mangled names in cc1
Date: Fri, 16 Mar 2012 13:24:00 -0000 [thread overview]
Message-ID: <20120316132417.GA10877@ours.starynkevitch.net> (raw)
In-Reply-To: <87ty1ou26x.fsf@inria.fr>
On Fri, Mar 16, 2012 at 02:04:38PM +0100, Ludovic Courtès wrote:
>
> What about writing it in C++? Function objects could be passed around
> to achieve a similar result, at the expense of conciseness and
> interoperability with C.
Well, if your plugin is compiled with C++ and all of GCC is also compiled with C++, you might not need interoperability.
> This is an unfortunate collateral damage, IMO.
>
> Thanks,
> Ludo???.
>
> [0] https://gforge.inria.fr/scm/viewvc.php/trunk/gcc-plugin/src/starpu.c?view=markup&root=starpu
By the way, your plugin could be an interesting case for MELT, which
obviously provide higher-level functions (since MELT functions are true
closures).
Cheers.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
next prev parent reply other threads:[~2012-03-16 13:24 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 9:51 Ludovic Courtès
2012-03-09 9:54 ` Andrew Pinski
2012-03-09 10:00 ` Jakub Jelinek
2012-03-09 10:41 ` Ludovic Courtès
2012-03-09 13:26 ` Ludovic Courtès
2012-03-09 14:17 ` Duncan Sands
2012-03-09 14:57 ` Ian Lance Taylor
2012-03-09 15:42 ` Ludovic Courtès
2012-03-09 16:01 ` Ian Lance Taylor
2012-03-09 17:00 ` Ludovic Courtès
2012-03-09 18:08 ` Ian Lance Taylor
2012-03-12 8:56 ` Ludovic Courtès
2012-03-12 12:11 ` Richard Guenther
2012-03-12 12:31 ` Gabriel Dos Reis
2012-03-16 11:04 ` Ludovic Courtès
2012-03-16 11:05 ` Richard Guenther
2012-03-16 13:04 ` Ludovic Courtès
2012-03-16 13:08 ` Richard Guenther
2012-03-16 15:17 ` Ludovic Courtès
2012-03-16 18:48 ` GCC 5? (was Re: GCC 4.7.0RC: Mangled names in cc1) David Malcolm
2012-03-16 19:03 ` Diego Novillo
2012-03-16 19:29 ` Gabriel Dos Reis
2012-03-16 19:42 ` Joseph S. Myers
2012-03-18 16:56 ` GCC 5 & modularity Basile Starynkevitch
2012-03-18 17:11 ` Robert Dewar
2012-03-18 17:53 ` Basile Starynkevitch
2012-03-18 20:49 ` Jonathan Wakely
2012-03-19 5:57 ` Basile Starynkevitch
2012-03-19 10:04 ` Jonathan Wakely
2012-03-19 10:57 ` Gabriel Dos Reis
2012-03-16 20:22 ` GCC 5? (was Re: GCC 4.7.0RC: Mangled names in cc1) Jonathan Wakely
2012-03-19 10:08 ` Richard Guenther
2012-03-19 15:37 ` Ludovic Courtès
2012-03-19 15:58 ` Richard Guenther
2012-03-20 11:47 ` Ludovic Courtès
2012-03-20 12:07 ` Richard Guenther
2012-03-19 18:04 ` Gabriel Dos Reis
2012-03-16 13:24 ` Basile Starynkevitch [this message]
2012-03-16 17:40 ` GCC 4.7.0RC: Mangled names in cc1 Gabriel Dos Reis
2012-03-19 9:57 ` Ludovic Courtès
2012-03-19 10:54 ` Gabriel Dos Reis
2012-03-19 15:46 ` Ludovic Courtès
2012-03-16 17:35 ` Gabriel Dos Reis
2012-03-12 12:30 ` Gabriel Dos Reis
2012-03-10 1:25 ` David Malcolm
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=20120316132417.GA10877@ours.starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.org \
--cc=ludovic.courtes@inria.fr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).